Adytum
Launch app

The trust rule

This page lists what the spike program and the production program enforce, each measured on a local validator, and what the spike does not enforce.

Enforced in the spike

RuleHow the program checks itTest result
An exit pays only the key that signed itEach exit must be preceded by an ed25519 verification instruction whose public key and message match the exit's address, amount, root and batch number; the payout account must equal that addressA settle carrying a forged signature was refused
Only the sequencer posts a settleThe signer must equal the sequencer key stored in the domain accountA settle signed by another key was refused
Each batch counts onceThe signed message includes the batch number, and every settle moves it forward by oneReplaying a settle with an old batch number was refused
The vault is the domain's ownThe vault address must equal the address derived from "vault" and the domainChecked on every settle

Enforced in the production program

The production program (engine-domain) passed 36 of 36 tests on a local validator, eight of them attacks.

RuleTest result
A member leaves by signing readable words: "Adytum exit", the domain, the amount in SOL and the batch number. The vault rebuilds that text and pays only the wallet whose key signed itAn exit signed by another key, for another domain or for an old batch was refused
The signature proof must sit inside its own instruction at the standard positions, so the bytes the program reads are the bytes that were signedTwo forged layouts were refused, including the one that emptied a vault in the first build
One exit per member per batchThe same signed exit placed twice in one batch was refused
Inactivity exit: each domain sets a window of N slots when it opens. If no settle lands for N slots, a member can withdraw without the sequencer, taking a balance the sequencer signed at the last batch, or the deposits they made since itWithdrawal without the sequencer succeeded
Each receipt pays once per batch, and each deposit onceSecond claims were refused, including after a fresh deposit
A member's receipt account cannot be closed while the domain runs, so its claim records cannot be resetClosing it on an open domain was refused
The sequencer cannot settle until it has counted every inactivity exit the vault has paidA settle with a stale count was refused
The inactivity exit is only for a silent domainAn active domain refused it
Exits pay only wallets that enteredA settle paying a wallet that never deposited into that domain was refused
The domain closes only when its vault holds no member moneyClosing it with money inside was refused

The sequencer follows two rules of its own, checked through the app on a local validator (51 of 51 checks passed):

The sequencer can still hold the door shut by not posting settles. The inactivity exit is the way out when it does.

Not enforced on chain

On the roadmap

The sequencer moves into an attested hardware enclave, so the code that holds the room's keys can be checked.