The radar continuously polls each watched wallet (Helius), rebuilds its baseline, and alerts the moment a rule fires. The demo is a historical replay, not a confirmed incident: wallet 8XeK5m…eYXU2j, a wallet dormant for about 173 days wakes up with one swap of about $4,000 (about 4.7× its median) on a new venue, plus a new protocol and three new counterparties.
Because mainnet is immutable, re-running the detector on the same historical data reproduces the same verdict — radar replay 8XeK5m… --since 2026-03-11 --until 2026-08-31 → RISK 100/100 · 8 anomalies · 1,307-tx baseline.
Reproduce it yourself with scripts/verify-canon.sh; full write-up in LIVE-DATA.md.
radar_trust is that gate: it returns one decision —
safe / hold / unknown — with a per-rule reasons[] breakdown, a one-line
summary, and a freshness stamp on how recent the data is. An agent about to
copy-trade a wallet calls it first and stops, instead of sending money to a wallet that
just woke up. And radar_batch gates the whole book at once — it runs the trust
check over up to 20 wallets in a single call and returns a ranked shortlist of the ones
that are actually safe to copy right now. And once you are copying, the monitoring surface
keeps the gate open: the server watches the wallets on your list over HTTP
(/watch, /poll, /alerts) and fires a webhook the moment a new
anomaly appears — so the gate is continuous, not a one-shot.