Skip to main content
POST
Sign a deposit for omni

Body

application/json

A source chain deposit, as omni's DepositProof names it.

chain_from
integer
required

Chain ids are omni's (v2_1.omni.hot.tg), not always the chain's own: EVM chains use their EIP-155 id (Ethereum 1, Optimism 10, BNB 56, Polygon 137, Monad 143, X Layer 196, Base 8453, Arbitrum 42161, Avalanche 43114, ...); the others have omni's numbers: Solana 1001, NEAR 1010, Stellar 1100, TON 1117 (TON v1, 1111, is dead), Juno 4444118, Gonka 4444119.

Required range: x >= 1
Examples:

1100

1117

137

4444119

nonce
required

omni's nonce: a decimal string (preferred) or a JSON integer, read exactly even above 2^53. Hex, floats and negatives are refused.

Pattern: ^\d{1,39}$
Example:

"1792944123000000004211"

amount
required

A positive amount in the token's smallest unit: a decimal string (preferred) or a JSON integer.

Pattern: ^\d{1,39}$
token_id
string
required

omni's token id (base58 of the token's bytes on its chain; on Stellar of its ScVal XDR).

Pattern: ^[1-9A-HJ-NP-Za-km-z]+$
receiver_id
string
required

The deposit's receiver, base58 of its 32 bytes: the NEAR Intents receiver (deposit_hash).

Pattern: ^[1-9A-HJ-NP-Za-km-z]+$
sender_id
string | null

Ignored.

Response

The signature.

HOR's signature answer.

signature
string
required

The signature, base58. Withdrawals: 65 bytes in the target bridge's layout. Deposits and clears: 64 bytes, r ‖ s.

Pattern: ^[1-9A-HJ-NP-Za-km-z]+$
autopilot_hash
null
required

Always null; kept from HOR's answer model.