Documentation
Guides and reference for OutLayer verifiable compute and agent custody.
Docs navigation
Leaving OutLayer with your keys
A wallet’s keys are held in a TEE. Its owner can take them out and go on using the same addresses with no OutLayer service — and does not need a vault for that. There are two exits. Neither needs OutLayer’s API, dashboard or consent: each is a contract on NEAR, the NEAR MPC network, and a tool you run yourself.
Three kinds of wallet, two exits#
| Wallet with no owner | Owner exit | Vault exit | |
|---|---|---|---|
| How the wallet is made | POST /register | A NEAR account registers in the keystore DAO. Its wallets come from a link an agent hands over, or from the account’s own signature. | A vault contract is deployed on a sub-account; wallets are registered with its vault_id. |
| Set up by | nobody | one transaction from any NEAR account | one transaction that creates the vault account |
| Cost | nothing | 0.05 NEAR, once per account; 0.01 NEAR per exit | 1 NEAR kept on the vault account |
| Can the keys be taken out | no | yes, by the owner account | yes, by the vault’s parent account |
| Wait before the keys leave | — | 24–48 hours, chosen by the owner | 1–30 days, chosen at deployment |
| What leaves | — | the keys of every wallet of the owner | the keys of the vault’s wallets and every secret bound to the vault |
| Addresses afterwards | — | the same addresses, signed for with keys you derive | the same addresses, signed for with keys you derive |
| Coming back | — | the same account gets new wallets, at new addresses | the vault is out for good |
| Works if OutLayer stops | no | yes: the escrow of the keys is in the DAO contract, and the key that opens it comes from NEAR MPC | yes; and a cessation declared by the DAO opens recovery on its own |
| Can it be taken away | — | by an upgrade of the DAO contract, which runs no earlier than the governance delay after its vote — time to leave first | no: a vault’s code is fixed when it is deployed |
| Who can hold it back | — | the exit approvers, if the owner named any | nobody: the parent stands above every policy |
| Secrets | stay in OutLayer | stay in OutLayer | leave with the vault |
Which one#
- A wallet that holds value has an owner. The owner exit costs one small transaction and nothing to run. An agent asks for it with
POST /wallet/v1/exit-link, its user signs once on the Owner exit page, and from then on the user can leave with the keys whatever happens to the agent or to OutLayer. - A vault when secrets must leave too, or when no upgrade may ever touch the exit. An application whose secrets must be recoverable binds them to a vault. A vault’s exit is not subject to OutLayer’s governance at all.
- A wallet with no owner is for a start. It has no exit: its keys stay in OutLayer. It moves to a wallet with one at any time — a new wallet at a new address, the funds sent over by an ordinary transfer, venue accounts opened again under it.
What is the same for both exits#
- The exit is a transaction on NEAR from the account that owns it, a wait that account chose in advance, and a claim.
- The wait is on chain for anyone to read, and lowering it takes effect only after the wait in force has passed: a stolen key cannot shorten the time its victim has to react.
- After the exit OutLayer no longer serves those wallets and the wallet’s policy no longer applies.
- Funds held by a venue under a key of its own — a Polymarket or Hyperliquid account — are withdrawn before leaving.
The runbooks#
- Owner exit: docs/OWNER_EXIT.md
- Vault exit: docs/LEAVING_OUTLAYER.md