Settlement

Deferred Settlement and Atomicity

The protocol does not move tokens immediately. Every increase and decrease within a transaction accumulates in a transaction ledger, and the protocol checks whether it sums to exactly zero only when the transaction ends.

A single transaction might run a swap, add liquidity, deposit real tokens and withdraw others. Each of those writes its own entries to the ledger. Only at the end does the protocol add them up, once per asset. If any total is not zero, the entire transaction reverts — partial success does not exist.

How Each Position's Share Is Computed

The pool maintains a single running counter: cumulative fees per unit of liquidity.

Each position computes only the difference between the value it last checked and the current value as its own share, and uses the values recorded at each boundary to isolate exactly the time it was active. The calculation is fully independent per position.

A Single Vault, a Separate Ledger per Engine

All assets live in a single Vault. Pool engines only instruct the Vault; they never hold assets directly.

The Vault keeps a separate custody ledger — a permanent balance — for each engine, and an engine can reach only its own. A flaw in one engine therefore cannot touch assets managed by another.

The protocol ends up with a two-layer defense: the time axis, meaning per-transaction integrity, and the space axis, meaning per-engine asset isolation.