Settlement
Move verified agent spending from escrow to the provider, and commit the evidence root that justifies it — in one transaction.
Settleable now
0
confirmed on chain, inside expiry
Claims to settle
0
would move to providers
Remainder
0
stays in the vaults, refundable to agents
Settleable sessions
Unsettled and still inside their expiry window
No settlement yet
Choose a session on the left to see exactly what would move, and to whom. Nothing is submitted until you confirm.
What this transaction does
The program re-checks the claim before it moves anything: still inside expiry, higher than what was already settled, no more than the deposit, and carrying a valid Ed25519 signature from this session's agent. The gateway's opinion does not enter into it.
It then transfers only the difference between this claim and what was settled before. Claims are cumulative, so paying the highest one pays for every call beneath it — one transfer, not one per request.
It writes a SettlementRecord holding the claim hash, the Merkle root and the cumulative amount. That record is what makes a decision provable to someone who was never given the log.
Settlement can run more than once. Under program v2 it is monotonic: a later settlement may commit a higher cumulative total and a newer root, and may never lower either. That is why the root above is the latest committed one rather than a final one.
The remainder stays put. Settling does not return it — it sits in the vault until refund_session runs, which after expiry anyone can call, because those funds can only ever move to the agent.