Numbers · ERC-8004
Do agents registered on ERC-8004 actually transact?
Sato Hub holds no reading of what ERC-8004 registrants did this week on any chain, so how many transact is unknown rather than zero, as of 2026-09-14.
No reading has been banked yet. That is unknown — not an answer of zero, and not evidence that registrants are idle. The measurement runs weekly; this page fills in when it does.
This is a sample of owner keys, not a census of agents
The roster we can enumerate without an explorer key is a trailing window of registration logs, so the wallets sampled here are recent registrants — the busiest slice of the registry, not a picture of it. The figure is never multiplied out to the registry's counter, and the two chains are never added together.
It also measures the owner key, in both directions at once: a person moving funds from the same wallet counts, and work an agent did through a smart account, relayer, paymaster or session key does not. A wallet that registered inside the window sent a transaction to do so, which is why the “more than once” column sits beside the headline rather than under it.
- Method
- Not yet measured.
- Why not logs
- Because no public node answers “what did this address do”.
eth_getLogsfilters on the contract that emitted a log, never on the wallet that sent the transaction, so a sender-side filter does not exist without a keyed explorer. The account nonce does, and its movement is what is counted. - Contract owners
- Excluded. A contract's nonce counts the contracts it has deployed, not the transactions it sent, so a delta there means something else entirely. They are counted apart rather than folded in.
- Related
- The registry census is on agents by chain and its weekly trend on registered agents.
Questions this page answers
- How many ERC-8004 registrants transact in a week?
- Sato Hub holds no reading on any chain, so the answer is unknown rather than zero.
- How is it measured, without an explorer key?
- By the movement of each owner wallet's transaction count: the nonce at the head of the chain minus the nonce 7 days earlier, read over public RPC. There is no keyless way to ask a node what an address did — eth_getLogs filters on the contract that emitted a log, never on the wallet that sent the transaction — so the nonce delta is what a public node can answer.
- Does this mean the agent did something?
- Not exactly, in both directions at once. A nonce delta counts every transaction the owner KEY sent, so a person moving funds from the same wallet counts. It also counts nothing an agent did through a smart account, a relayer, a paymaster or a session key, so work done that way is invisible here. And a wallet that registered inside the window sent a transaction to do so — the table shows the count with that single transaction taken off, beside the headline.
- Is this a share of everyone on the registry?
- No, and the difference matters. The roster we can enumerate without a key is a trailing window of registration logs, so the sample is drawn from RECENT registrants. Recent registrants are the busiest ones, so this is an optimistic slice, and it is never multiplied out to the population.
- Why is a share missing for some chains?
- It is not missing on any chain here — every sample cleared the 20-observation floor. Where a sample does not, the counts are shown and the share is withheld.
Sources — the standard these registrations follow
Data CC-BY-4.0 — attribution: data by satohub.ai. Unknown is a value here and never means zero.
Cite this page
Sato Hub. "ERC-8004 registrants that sent a transaction in the trailing week." Sato Hub, updated 2026-09-14, accessed 2026-09-14. https://satohub.ai/numbers/erc-8004-agents-that-transactData last refreshed 2026-09-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.