The Escape is the way out that needs no enclave. If no Commit lands for more than 9,000 slots, about 30 minutes, the Pool freezes at its last committed root, and every owner takes their last committed balance out of the vaults with the Council’s shares and their own escape key. On Account, the Escape panel shows the frozen state and your request’s progress.
When it opens#
The Coprocessor commits whenever a Crossing settles something, and at least every 750 slots, about 2.5 minutes, with nothing to settle, so Commits stop only when the enclave does. Trust shows the Last Commit slot and Escape could open in, a count of slots. Once the window passes, anyone can call trigger_escape, and Privium’s keeper calls it as soon as it can (When it opens).
From the trigger on, the Pool takes no Commits, no Residual swaps and no deposits. Orders and Exit requests not yet in a committed root lapse, and the balances they would have changed are paid as the last Commit left them.
Where the app shows it#
| Where | What it shows |
|---|---|
| Trade | The ticket reads “Trading is closed while the Escape is open” with Open the Escape panel in place of the order form (What the ticket asks for first). |
| Trust | Liveness reads Escape open, Frozen at slot with the slot, and Take out your last committed balance. |
| Account | The Escape panel, headed The Escape is open, leads the page above Account value, which reads “Frozen at root” and the root; the Deposit and Exit forms pause (Deposits closed during the Escape). While it rebuilds your balances it reads “Recovering your balances from the Pool’s public diffs, checked against the frozen root.”, and History reads “History is read through the Coprocessor, which stops during the Escape. Your balances above come straight from the frozen root.” |
The Escape panel#
The panel opens on Account while the Escape lasts. Its line reads “No Commit landed for 9,000 slots, so the Ledger froze at its last root. Request each balance, and it leaves the vaults to the address you name once t of the Council’s n members have posted their shares.” On mainnet that is 5 of 9.
At its head, Frozen root is the root of the last accepted Commit, the root every request proves its leaf against, and At slot the slot that Commit landed. Under it, one card for each asset you hold in the frozen Ledger:
| Part of a card | What it shows |
|---|---|
| Balance | Your committed balance in that asset, the amount a claim pays. |
| Request | Your request’s address for that asset, derived from your leaf and the mint. |
| Council shares | The Council’s n members as dots, the first t marked as needed, one filled for each share that lands, and the count, “k of the t needed”. |
| Steps | Your request is on chain, Council shares arriving, Ready to claim to your address, and Paid with a Transaction link. |
| Shares | Each share that landed, as “Member m” with a share link to its transaction. |
With nothing of yours in the frozen Ledger, the panel says “Nothing of yours is in the frozen Ledger.”
Take out a balance#
Request it#
On the asset’s card, press Request and the asset’s symbol. The request goes on chain through the API’s relay, with no wallet prompt; the card moves to Your request is on chain.
Watch the shares#
Council members post their shares on their own, and the card fills a dot for each, “k of the t needed”, moving to Council shares arriving. The card follows them every 4 seconds until Ready to claim to your address.
Claim it#
A To address field opens, filled with your wallet’s address; change it to any address you choose. Press Claim with the amount and symbol. The claim’s proof binds that address, so whoever relays it pays only there. The card moves to Paid with the transaction.
Do this once for each asset card.
Request states#
| State | The panel shows | What it means |
|---|---|---|
| Requested | Your request is on chain | The program verified your leaf against the frozen root and opened your request. |
| Collecting | Council shares arriving, “k of the t needed” | Shares are landing; each is checked against its member’s key on its own. |
| Claimable | Ready to claim to your address | valid shares are in, and the program stored their combination. |
| Paid | Paid, with the transaction | The claim landed and the balance left the vaults. A leaf is paid once. |
A claim pays your committed balance in the asset you hold. If a Crossing was open with Residual swaps already executed when the Pool froze, every holder of the asset those swaps spent takes a proportional share of what they received (The settlement rule).
From code#
The panel runs three calls of the SDK on your account, members of Privium:
requestEscape({ asset })files the request for your balance in one asset.watchEscape(request)yields the request’s state each time it changes, until it is paid.claimEscape({ request, destination })claims a request’s balance to the address you name, once its shares are combined.
Both the request and the claim go through the API’s relay, whose fee payer submits them (Escape requests and claims), so neither takes a wallet prompt. The escape key derived from your one signature makes the claim’s proof, which holds for exactly your committed balance and the destination you named (Claiming a balance).
Deposits refunded#
A deposit that landed in a vault shard and was not credited by a Commit before the trigger returns to the token account it came from, through refund_deposit, which the keeper cranks and anyone can call. Its row above your balances reads “refunded to your wallet: the Escape opened before its Crossing credited it”. New deposits are refused while the Escape is open (Deposits closed during the Escape).
Exits still released#
Every Exit piece a Commit already listed in its exits root keeps releasing, exactly as before the trigger, each release one transfer to its destination (Exits). A piece still sealed at the trigger never entered a committed root; its amount is part of the balance your claim pays.
When the app answers#
“The request did not go through.”#
The relay refused the request or could not reach the chain; the card shows the reason when there is one. Press Request again.
“The claim did not go through.”#
The relay refused the claim or could not reach the chain. Check the address in To address and press Claim again; a balance is paid once, so a second claim of a paid request is refused.