CATALORAKeepers
Every halt on this site, every session state a mandate is checked against, comes from somewhere. A keeper posts $CATA to vouch for that data. Misreport it and the bond is forfeit — the oracle everything else depends on has money behind it, not just a promise.
Active keepers
0
Session-state and settlement, combined
Bonded
0 CATA
Forfeited to date
0 CATA
Taken from a keeper's bond, never from allocator capital
Active keepers
Nobody is bonded as a keeper yet.
Post a bond
A role is fixed once bonded. Withdraw and re-bond to switch which claim you are vouching for.
What a keeper vouches for
Session-state: the open / pre / post / closed / halted flag every mandate check and the assistant’s tools read. Settlement: the fills that become permanent, unfalsifiable rows in the track record. Both are load-bearing — a wrong halt flag freezes trading that should be live, and a wrong settlement corrupts a record the whole product claims cannot be corrupted.
Halts
The one piece of session state no clock can derive. Every halt below — and every drawdown pause and frozen order it causes — traces back to a bonded session-state keeper reporting it, not to a seed file.
Active halts
Nothing is halted right now.
Report a halt
Refused unless the address is bonded as a session-state keeper, and refused again if the ticker already has an open halt — one active halt per name, not a stack of them.
No transaction is signed and no $CATA moves. This records the bond the staking contract will later hold, and there is no automated way here to detect or punish a misreport — only to record one if it is ever confirmed.