Case file · About this instrument
About The Judge
The Judge traces stolen value across on-chain ledgers and produces the artefacts a fraud desk files: the trail, the terminal it names, and the freeze request that follows. It began as a fact-checking assistant and that earlier product is still here, marked as such.
What it does
A desk receives a fraud report with two facts: the address the money left from and the transaction it left in. The Judge follows that value forward — hop by hop, ordered in time, never sideways — and reports where it stopped. A trail that ends at a labelled exchange is a freeze request; one that ends at a mixer is a documented loss of provenance; one that ends at an unlabelled wallet is an honest unknown.
The same engine screens wallets at onboarding, producing a verdict band and the signals behind it, and can watch an address and report when its reading changes. Findings can be published as signed, content-addressed batches another desk verifies without trusting this one.
How it holds to that
- Forward only, never sideways
- Value moves from one address to another. Following an inbound edge would trace the victim's own history and report a path that predates the theft, so the tracer never does.
- An unknown stays unknown
- An unlabelled address is never assumed benign and never guessed at. A missing classification is reported as an absence of data, because a false “this is fine” is worse than a missing one.
- Provenance on every figure
- A label carries the publisher's URL and the date it was read. A claim a venue scoped to one ledger is never applied to another. A read that hit a cap says so on the face of the result.
- Measured, not claimed
- Every response carries a validation block splitting fired rules into those measured against real addresses and those evaluated only on synthetic data. The benchmark's honest numbers — including the weights that were fitted while viewing the corpus — are stated in the docs, not buried.
Limits
The engine walks six EVM ledgers plus Tron; only Ethereum is validated end to end, and the chain page says which is which. A live trace is bounded by an explorer rate budget and a wall clock, and a trail cut short by either reads as a lower bound, never as the whole picture. Institution names come from the the venues’ own publications, attributed — a venue’s assertion, not our finding — and a jurisdiction, where one is shown, comes from a cited mapping rather than inference.