The difference is what you can defend
Most tools hand your analysts a number and ask them to trust it. When a regulator, a bank, or a court asks how you reached a decision, a number is not an answer. The Registry gives you the evidence instead, and draws a hard line around what it will and will not claim.
Evidence, attached to every line
- ✓The mechanism, not a guess. One of four kinds of evidence: a settled on-chain event, a property of the contract's own code, a capability demonstrated in a state-override simulation, or membership of an official sanctions list. A fact, at a stated block.
- ✓A certainty tier on everything. Tier 1 is a settled fact. Tier 2 is proven by replay or simulation at the block. You always know how strong the ground is before you act.
- ✓The full receipt. Every entry ships with the evidence that proves it and a step-by-step recipe to reproduce the result.
- ✓Proof anyone can check. A content hash your team rebuilds from the cited evidence and reproduction steps — on your own node for chain facts, against the issuing authority's list for list entries — without taking our word for it.
Nothing you would have to defend
- ✕No risk score. We never reduce an address to a number you cannot explain to a regulator.
- ✕No claim about a person. Mechanisms and addresses only. Never an identity, never a motive.
- ✕No accusation you cannot stand behind. Softer, grouping-based signals stay on a separate advisory lane, clearly labelled as inference.
- ✕No black box. Nothing on this record is something you have to take on faith.
From the cited evidence to proof you can take to court, in three steps
There is no model to audit and no black box to take on trust. Anyone on your side of the table can walk the same three steps and land on the same answer.
The cited evidence demonstrates the entry
One of four kinds: a settled on-chain event, a property of the contract's own code, a capability demonstrated in a state-override simulation at the block, or membership of an official sanctions list. Tier 1 when it is a settled fact, tier 2 when it is proven by replay or simulation; a listing is checked against the issuing authority's published list.
We capture the receipt
Every entry keeps its evidence word for word, plus a recipe to reproduce it — transactions and log indices for an on-chain event, bytecode and eth_call reads for a code property, the state-override calls for a simulated capability, the issuer's list and entry for a listing — and the method used.
You recompute the proof
A sha256 over the entry is its name. Rebuild it from the cited evidence and reproduction steps and the hash matches — on your own node for chain facts, against the issuing authority's list for list entries — on your own terms.
The record you get access to, today
These figures are live from the register right now. Every one is an entry the cited evidence demonstrates — a mechanism, a code property, a simulated capability, or an official listing — and each carries its own proof, ready to cite.
Every kind of catch, replayed from a real case
Pick a mechanism. Each one is a real entry from the register, played back from its own receipt: what the evidence names, its cited receipt at the block (transactions and reads, state-override calls, or the issuer's list), the arithmetic, and the hash that closes it. Watch them all, or step through one beat at a time.
in the row's receiptdeep-store context, outside the hashthe subject's value movingrecomputable · /v1/verify
Evidence your whole desk can stand behind
Built for the people who have to answer for the decision: exchange compliance, financial crime units, and the firms that advise them. One subscription puts the whole record, and the proof behind every line, in your team's hands.
- The whole record, every morning. A signed daily snapshot you can archive, diff, and cite in a file.
- Screen at the scale of your book. Bulk API and exposure checks, so a name clears or flags with its evidence attached.
- More for your analysts. The advisory lane, clearly labelled, for the softer signals that guide a look without making a claim.
- Own your evidence. Screen, investigate, and cite. Recompute any entry yourself — on your own node for chain facts, against the issuing authority's list for list entries — and never depend on us to defend it.