The TRITO Notary
Independent corroboration for anyone who needs to prove a value existed at a point in time — and that a group of unrelated machines, chosen at random, recorded it independently.
What it actually does
An organisation — a rollup, an exchange, an auditor — periodically produces a summary of its own state: a single hash standing for everything that happened in a period. They file that hash with TRITO.
When the next slot opens, three TRITO nodes are drawn at random by Chainlink VRF, weighted by reputation earned over months. Those three independently fold the filed hash into the value they attest. Two of them must arrive at the same answer for the slot to seal.
What that produces is a record anyone can check: this value was filed by this party, in this slot, and independently recorded by a committee nobody chose.
What it does not do
TRITO's nodes cannot verify what a checkpoint means. They have not executed the filer's chain, do not hold its state, and could not detect a fraudulent root if one were filed.
This is timestamping and corroboration — not validation, not fraud proofs, not a guarantee that the underlying data is honest. A party filing nonsense about itself gets nonsense faithfully recorded.
We state this plainly because a corroboration service that oversells its own guarantee is worse than none. Verifying correctness would require running the filer's chain — a different service, with different economics.
Recent checkpoints
0 filed · 0 registered consumersNo checkpoints filed yet.
Read directly from the notary contract at 0xbAb7…7685. Nothing here is reported by us — every row is a call you can make yourself.
What it costs
Bond, refundable
0 TRITO
Collateral, not a fee. Returned in full when you leave — it earns nothing while held, and there is a notice period before withdrawal.
Per checkpoint
0 TRITO
Charged when you file. File once a day or once a minute — the bond does not change.
Where each fee goes:
The machines that corroborated it — split between the members who agreed
The operator share has a floor written into the contract — it cannot be set below 40%. Revenue that never reaches the machines producing the service is extraction, and that is the parameter that drifts downward one governance vote at a time unless something refuses.
How to integrate
1. Register once, posting the bond.
2. Call submitCheckpoint(bytes32) whenever you have a value to record. It is stamped with the open slot and frozen when that slot closes.
3. Read checkpointStatus(id) to see when the covering committee has corroborated it.
There is no API key, no account, and no service to trust: filing and reading are both contract calls. If TRITO disappeared tomorrow, everything already corroborated would remain provable.
Testnet deployment. Terms and parameters may change before mainnet.