The Judge

Fraud investigation · evidence-grade

A customer was scammed.
Where did the money go?

Give The Judge the address the value left from and the transaction it left in. It follows that value forward — hop by hop, never sideways — names the exchange, mixer or bridge it reached, and produces the freeze request a desk can actually send. Every figure carries where it came from, because a finding that cannot be checked cannot be filed.

9 of 10
rules measured against real addresses

The validation block in every response splits fired rules into those measured against real addresses and those evaluated only on synthetic data — so no one can over-trust a result.

815
addresses in the tuning corpus

Precision 0.818, recall 0.818, false-positive rate 0.063 — those weights were fitted while viewing that corpus, and the docs say so rather than presenting the figure as production accuracy.

297k
venue-published addresses

Institutions' own proof-of-reserves publications, attributed with the source URL and retrieval date, scoped to the ledger the claim is about — the difference between a name and an assertion.

Forward only, never sideways

Value moves from one address to another, so the trail follows it that way. An undirected hop search would trace the victim's own history and report a path that predates the theft.

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 the venue scoped to one ledger is never applied to another. A truncated read says so on the face of the result.

Open a case

The victim's address and the theft transaction are enough to start. Nothing is stored, nothing is shared, and the trail you get is the same trail you would get again tomorrow from the same inputs.

Start a trace