Adytum
Launch app

Measured numbers

All figures come from one run of spike-domain/client/loop.mjs against a local Solana validator on 18 November 2026. The script is rerunnable from scratch.

StepCompute unitsTransaction size
Open a domain7,419398 B
Deposit2,574278 B
Private transfer (off chain)00 B on chain, 448 B encrypted transcript
Batch settle with two exits3,948873 B

Production program

Measured by the engine-domain test suite (engine-domain/client/test.mjs, 36 of 36 passed) on a local validator. The production program does more work than the spike: it rebuilds the readable exit text the member signed, checks that each signature proof sits inside its own instruction, and keeps a lifetime deposit total per member. Compute varies by a few thousand units between runs because address derivation tries a different number of seeds for each address.

StepCompute unitsTransaction size
Open a domain7,458 to 14,958406 B
Deposit, first (creates the member's receipt)12,994311 B
Deposit, later10,490311 B
Settle with one exit20,973662 B
Settle with two exits34,845981 B
Settle with no exits (heartbeat)2,726 to 10,226311 B
Inactivity exit, sequencer receipt4,980544 B
Inactivity exit, deposits since the last batch4,562 to 13,562312 B

How many exits fit

Every exit adds one ed25519 verification instruction carrying the member's signed exit text, and one payout account.

Exits per settleSizeFits in 1,232 B
2981 Byes
3about 1,300 Bno

The sequencer sends at most two exits per settle and settles every few seconds. Settles are signed by the sequencer, so they may use address lookup tables later, and a batch can also be split across several settle transactions.

For scale

Solana gives one instruction 200,000 compute units by default. A deposit uses about 1.3% of that.

Rejections in the same run

AttemptResult
Settle with a forged member signatureRefused
Settle signed by a key other than the sequencerRefused
Replay of a settle with a stale batch numberRefused