An Exit is the normal way out of the Pool: a withdrawal from the trader’s Ledger balance to any Solana address, a Helius Ring deposit included. The trader signs it like an Intent, it runs as denominated pieces that the enclave schedules one by one, a Commit lists each piece in its exits root once its release slot has come, and anyone can release it from the vault.
The exit Intent#
An exit Intent names an asset, an amount, a destination and whether that destination is an address or a Ring deposit. The account’s auth key signs it with a fresh nonce, so it takes no wallet prompt, and it travels like any Intent, sealed to the Coprocessor’s attested key and relayed. The destination and the split stay off chain until each piece is paid.
The SDK splits the amount into denominations in the browser and seals one exit Intent per piece (exit). The enclave checks that the unreserved balance covers each piece, the balance less what the account’s open orders and scheduled pieces already hold, and refuses a piece it does not cover. It splits the piece’s amount by the same rule, so a denominated piece stays one piece, and draws its delay. The app shows the split and the exit delay before the trader confirms (Exits).
Denominations#
Denominations are binary multiples of a unit that each admitted asset declares, its denomination unit in the market list: one hundredth of a whole token, base units for a mint with decimals, and one base unit below that. The SDK and the enclave both split with the declared unit, into one of 24 multiples:
An Exit of amount runs as one piece for each set bit of , and each piece is an Exit of its own. The remainder below stays in the Ledger balance. One denominated Exit covers up to , about 168,000 whole tokens of a mint with two or more decimals.
A piece’s amount takes one of 24 values, shared by every piece of its class whichever account exits it, which tells an observer at most bits about its owner.
The delay#
When the enclave accepts a piece, it draws an independent delay from the exponential distribution with mean , rounded up to whole slots, and sets the piece’s release slot that far past the slot intake received it. The schedule stays inside the enclave: it shows each piece’s release slot to the account’s owner alone, in the encrypted status reply, and nothing of a scheduled piece reaches the chain, so an observer who has waited any number of slots learns nothing about the time remaining. The mean is set in configuration; the whitepaper recommends 9,000 slots, about 30 minutes.
The delay caps a timing analyst’s chance of naming a piece’s source deposit, whatever the trader’s own habits:
where is the rate per slot of honest deposits in the piece’s denomination class. Doubling the deposit rate or the mean halves the bound. The pieces of one Exit are delayed independently, so they land interleaved with other accounts’ pieces and do not read as one Exit.
From request to release#
- Requested. The account signs and sends each piece’s exit Intent.
- Scheduled. The enclave has accepted the piece and holds its release slot. Its amount stays in the Ledger balance, reserved, so the account’s new orders and Exits draw only on what is left. Nothing is on chain, and no public route knows the piece.
- In Commit k’s exits root. The first Crossing k opened at or after the piece’s release slot debits the leaf and lists the piece in the Commit’s exits root . Each Exit leaf commits to the Crossing, its index in the root, its origin (the Crossing and index of the Commit that first listed it), the mint, the recipient, the amount and the release slot. The piece’s amount enters that Commit’s Exits for its asset, added to the asset’s committed, unreleased total , which the conservation check counts until release. The piece is releasable as soon as the Commit lands, and the API’s public Exit record serves it from then.
- Released.
release_exitverifies the Exit leaf’s Merkle path against the exits root of a Crossing that lists it, creates thePaidRecordat the piece’s origin that blocks a second release, lowers and pays the recipient from the vault. The instruction is permissionless: Privium’s keeper calls it for every committed Exit, and anyone holding the leaf’s path can call it too.
LedgerRoot keeps the exits roots of the last 64 Commits, each with its Crossing index, in a ring that every Commit advances by one. A release proves inclusion against a Commit that listed its piece, with no account per Crossing.
A piece still unpaid 60 Crossings after Crossing , the last whose Commit listed it, is listed again in Crossing ‘s exits root, four Commits before ‘s root leaves the ring. The new leaf carries the new Crossing and a new index, and the same origin, mint, recipient, amount and release slot. Its amount stays in once, since a Commit’s Exits count only the pieces it lists for the first time, and the PaidRecord sits at the origin, so the piece pays once through whichever root lists it. Committed Exits keep releasing during an Escape.
Destinations#
| Destination | Where the tokens arrive | What the chain shows |
|---|---|---|
| Any address | that address’s token account | one transfer per piece from a vault: asset, amount, destination, slot |
| Helius Ring deposit | a Ring balance whose assets and amounts are encrypted from then on | one transfer per piece into the Ring deposit |
Through a Ring the funds pass a second, independent mixing stage. The chance of linking the deposit wallet to the wallet that finally withdraws from the Ring is at most the smaller of the two stages’ linking chances. The API’s lookup for Ring deposit addresses is in Ring deposits.