A deposit moves tokens from your wallet into the Pool with one wallet transaction. It lands in a vault shard drawn at random, carries a note only the enclave can open, and the next Commit credits your encrypted balance.
Make a deposit#
Open the Deposit form#
On Account, Deposit sits beside Exit above the form. While the account is empty the form stays on Deposit, and your balances read Nothing here yet. On Trade, an open account with no balance sees “Deposit to trade” in the order ticket, “Fund the account once; every market draws on it.”, with the same form offering the pair’s admitted quote and base assets.
Pick the asset and amount#
Asset lists the assets the Pool has admitted. Type the Amount in whole tokens. In your wallet shows what the connected wallet holds of that asset, and Max fills it in; for SOL, Max leaves a little in the wallet for network fees. On Account, In your account after shows what you will hold of the asset once the deposit credits, and Credits reads “At the next Crossing”. Once an amount is typed, a line under the form names the asset’s denomination unit: “Credits in units of unit asset.”
Press Deposit#
The button names the deposit, Deposit amount asset. The app builds the
deposittransaction: your tokens into one of the asset’s vault shards, chosen uniformly at random, with a note sealed to the enclave’s key that names your account’s public keys. The button reads Sign in your wallet, with a spinner, while the transaction is built and the wallet holds it, then Depositing until the Commit credits it.Approve it in your wallet#
This is the one wallet transaction a deposit takes, and the wallet pays its network fee. A wallet that sends its own transactions signs and sends it; a wallet that only signs approves it once, and the app sends the signed transaction through the API’s RPC relay.
Watch it land and credit#
A list of steps under the button follows the deposit to its credit, and a line above your balances shows it until then. When the Commit credits it, the balance updates, checked against that Commit’s root.
Deposit states#
| State | The app shows | What it means |
|---|---|---|
| Signing | Sign in your wallet | The wallet holds the transaction for your approval. |
| Sent | Sent, with a Transaction link to the explorer; above your balances, “amount asset sent; credits at the next Crossing” | The transaction is sent and has not landed yet. |
| Landed | Landed in a Pool vault; above your balances, “amount asset landed in a Pool vault; credits at the next Crossing” | The tokens are in the vault shard and the deposit is in that shard’s queue. |
| Credited | Credited at Crossing k | The Commit of Crossing k credited it. The balance is yours to trade and exit, and History lists a Deposit entry with its transaction. |
| Refunded | “The Pool could not read this deposit’s note, so the next Crossing returned it to your wallet.”, with a Refund link to the transaction; above your balances, “returned to your wallet: the Pool could not read its note” | The enclave could not read the deposit’s note, and the next Crossing paid the amount back to the wallet it came from (below). |
| Refunded in the Escape | Above your balances, “refunded to your wallet: the Escape opened before its Crossing credited it” | The Escape opened while the deposit waited in its queue, and refund_deposit returned it to the token account it came from. |
Each Commit credits every queue entry that landed since the one before, so a landed deposit is credited once, by the next Commit. A landed deposit is work for the Coprocessor, so its Crossing begins once 4 slots, about 0.8 s, have passed since the last Commit (The batch, The deposit queue).
A deposit whose note the enclave cannot read as a valid note for its account credits no balance, and its Crossing commits all the same. That Commit lists the amount as an Exit back to the wallet that owns the source token account, due at once, and release_exit pays it; the deposit then reads refunded, with the release transaction.
What the chain shows#
The form on Account says it under the button: “A deposit is the one transaction that shows your wallet on chain.” The transaction shows your source token account, the asset, the amount, the slot and the vault shard, with the sealed note. It does not show which Ledger leaf it credits, and nothing you do after the credit names the wallet (What an observer sees).
When the app answers#
The form’s message appears in red under the button, and nothing moves until a transaction lands.
The wallet declined#
The wallet’s own message shows, or “The wallet declined to sign.”, and nothing was sent. Press Deposit again and approve the transaction.
Deposits closed during the Escape#
While the Escape is open the Pool takes no deposits. On Account the Deposit and Exit forms give way to “Deposits and Exits pause while the Escape is open. Each balance leaves through its claim above, to the address you name.”, and a build that reaches the API is refused with ESCAPE_ACTIVE, its message under the button. A deposit that landed before the Escape opened and was not yet credited is refunded to its source, and its row above your balances reads “refunded to your wallet: the Escape opened before its Crossing credited it”.
“More than your wallet holds”#
The button says so when the amount is above what the connected wallet holds of the asset. Lower the amount, or press Max.
“The deposit did not go through.”#
The build or the send failed for another reason, and the message under the button gives it when there is one. Check the asset and amount and press Deposit again.
An amount above what the wallet holds marks the field before you press anything. With none of the asset in the wallet, the button reads No asset in this wallet and stays disabled; on Account, when the form offers other assets, the line under it begins “Pick another asset above, or send some to this wallet first.”
The SDK runs the same deposit with deposit, and GET /v1/deposits/{signature} follows it through these states.