What our detectors caught.

Each rule's record

A drain-shaped payment, a dead endpoint and a confirmed theft cost very different amounts when the rule is wrong, so every rule carries its own record beside its latest fire: how often it fired, how many fires we later re-derived, how many held, how many we withdrew, how many came next to an address-poisoning attempt, and how many are live. A blank cell means we hold no record that could fill it. JSON · definition

Measured rules

Every rule above was run against synthetic data with known answers before it shipped: an adaptation of IBM's AMLSim that generates thousands of agent wallets with drains, retry storms, mint bursts and layering rings planted inside, then runs these very detectors over it (generator, validator and reports, Apache-2.0). Synthetic data measures the rules, not the chain: a number here says how a rule behaves on a shape, and nothing about how often the shape occurs in the real ledger. Weekly run of 11 October 2026, seed 20261010: 2,813 agents, 66,900 transfers, 189 planted patterns.

Also checked on the same run: the liveness ladder (2,813 of 2,813 agents at the level the published rule says), the pass-through rule (10 of 10 cases) and the address-poisoning matcher (12 of 12). The run repeats every Sunday; the table is updated at each release.

By kind · tap one to filter the log and read the rule

The log · newest first · tap a row for everything we hold on it

45,364 logged · 1,975 more with a Desk plan · JSON API · live incidents only · how the ranks work

Detection, incident, and the difference.

New, 11 October 2026: three corrections and a new kind. Retry storms and mint bursts are now found as runs with a peak: a storm is a run of payments to one payee with no gap over ten minutes and some ten-minute span holding fifty or more; a burst the same with sixty minutes and twenty-five. The calendar-hour buckets they replace missed every storm that crossed the hour mark: 10 storm detections were logged where the ledger holds 45, from 7 payer–payee pairs where there are 28, and 83 bursting addresses where there are 88. Rows logged before 11 October stay in the log as history. Every drain detection now carries a balance reading, how much of what the wallet held the payment took, read from the chain at the block before: on the 47 drain-shaped payments since February, 39 took 80 to 100 percent. It is evidence beside the rule, not yet a filter. And layering_fan is new: one agent paying four or more others the same exact amount within days, the one layering shape the chain has shown (ten all time, each a fleet being funded; no cycle and no scatter-gather in the 314,826 agent-to-agent payments walked on 10 October). A shape, never an incident. Lists are now capped with a warning instead of silently. Definitions: retry_storm.v2, mint_burst.v2, drain_pattern.v2, layering_fan.v1.

New, 24 September 2026: drain_pattern. A payment at least five times the agent’s previous largest, at least $250, to an address it had never paid, after at least three earlier payments. It is the shape a drained agent wallet leaves, and also the shape of a legitimate one-off purchase, so it is always a detection for a human to read, never an incident, and the agent is never named publicly. The reasoning →

A detection is an occurrence: it happened at a time, we can point at the evidence, and a reader could in principle have watched it happen. A detector that fired on a state would turn this page into a scoreboard, and a scoreboard of low scores is worth nothing to anybody. "This agent has never answered a probe" sits on the edge — it is a state — so it only becomes a detection after a streak of failures with no success ever recorded, which makes it an event about our own repeated attempts rather than a verdict on the agent.

An incident is a detection that is also a harm, and recent. Three kinds qualify: a retry storm, where an agent pays the same counterparty over and over and somebody is paying the fees for every attempt; an identity that changed owner under a binding people rely on, so the history they trust now belongs to somebody else; and signing delegated to an implementation nobody has vetted. Each counts as live for 72 hours, then stays in the log as a detection.

A mint burst is never an incident, however large. One address minting hundreds of registrations in an hour is exactly what a platform issuing identities for its users looks like. It is worth logging because it changes what a registration count means — the headline is measuring a script, not an ecosystem — but it harms nobody. This page called it a sybil burst until September 2026, and that was wrong: sybil asserts intent, and our own definition says the opposite.

Detectors that are armed and currently silent still matter. god_key_unknown_7702 fires when a wallet delegates to an implementation outside a curated allowlist, and that allowlist ships empty on purpose — until a human has read a contract and can say why it belongs there, calling an unknown implementation a god key would be a guess, and this site does not publish guesses. It reports nothing today, and that is the honest answer rather than a broken one.

Get these as alerts.

Everything live, and a morning digest: the Telegram group t.me/AgenticFinanceGraph posts each live incident as it is logged and a digest every morning. The digest is also how you know the feed is alive on a quiet day.

Your own agents: message @AgenticGraphBot and send /watch 57657 (an ERC-8004 number on Base, its slug, or the bound wallet). Free, three agents per chat. The bot tells you when our detectors log something on one of them, and /agent 57657, /top and /detections answer on demand. Every agent page has a Watch on Telegram button that opens the bot with that agent already watched. /stop deletes the chat's id and its list.

I joined the group but see no alerts: alerts post only when a detector logs a live incident, and the morning digest proves the feed is running. The bot did not answer /watch: send the agent's number, not its name. Email alerts are next. A chat watches 1 agent free, or 20 or 60 when it is linked to an Operator or Team Desk (/link).