How is the ERC-8004 registered-agent count trending on each chain?
As of 2026-10-19, registered ERC-8004 agent ids per chain, never summed: BNB Chain 376,540 (+4,347 on the week), Base 271,519 (+165,403 on the week), Ethereum 54,306 (+1,600 on the week) and 7 more chains.data: weekly readings, JSON · CSV · MCP onchain_agent_get_trend(venue="erc8004", stage="registered")
- As of2026-10-19
Each chain is its own registry, so there is no total. How many registered agents transact or answer is unknown for now: no sample of recent registrants is large enough to publish a share yet.
| Chain | Registered ids | Week over week | Last 12 weeks | Tier |
|---|---|---|---|---|
| BNB Chain | 376,540 | +4,347 (+1.2%) | 8 wk | 1 · proof |
| Base | 271,519 | +165,403 (+155.9%) | 8 wk | 1 · proof |
| Ethereum | 54,306 | +1,600 (+3%) | 8 wk | 1 · proof |
| Robinhood Chain | 8,865 | +84 (+1%) | 6 wk | 1 · proof |
| Gnosis | 4,167 | +9 (+0.2%) | 8 wk | 1 · proof |
| Avalanche | 1,847 | +2 (+0.1%) | 8 wk | 1 · proof |
| Arbitrum | 1,636 | +13 (+0.8%) | 8 wk | 1 · proof |
| Polygon | 690 | +4 (+0.6%) | 8 wk | 1 · proof |
| Optimism | 567 | +2 (+0.4%) | 8 wk | 1 · proof |
| Tempo | 345 | +30 (+9.5%) | 8 wk | 1 · proof |
One row per chain; no total, on purpose.
Why there is no totalShowHide
The number of agent ids the ERC-8004 Identity Registry holds on each chain where the singleton is deployed, read weekly from the contract itself — latest week starting 2026-10-19, read 2026-10-19. One row per chain. There is no total on this page, on purpose: a registration on one chain and a registration on another are different objects on different contracts, and the registrations counted here include test, duplicate and abandoned ids.
- Method
- lastAgentId (_lastId, ERC-7201 namespaced storage slot) on the singleton Identity Registry The Identity Registry is one contract deployed at the same address on every listed chain; the counter is read directly, so the count is exact for that chain on that day (evidence tier 1).
- Unit
- registered agent id. An id is minted by any call to register(); it says nothing about whether the agent is funded, active or real. The funnel after registration is on the venue page.
- Cadence
- Weekly (Monday run). Series start 2026-08-31; this page refreshes with the weekly job.
- Reproduce
- GET /api/export/adoption.json → rows where venue="erc8004" and stage="registered" · MCP onchain_agent_get_trend(venue="erc8004", stage="registered", chain=…)
Why sources disagree
Each tracker counts a different set of chains and decides what an agent is: every registered id, only ids with a registration file, or testnets too. A wider scope or a looser definition gives a bigger figure, so the figures cannot be lined up or added.
- 8004scan ↗1,531,897
agents · mainnet chains, agents with a registration file · all time
Agents 8004scan indexes in this view.
read 2026-10-24
- 8004scan ↗1,594,290
agents · mainnet chains, including ids without a registration file · all time
Agents 8004scan indexes in this view.
read 2026-10-24
- 8004scan ↗1,856,631
agents · all networks, testnets included · all time
Agents 8004scan indexes in this view.
read 2026-10-24
- agenteconomy.to ↗1,333,878
agents · the chains agenteconomy.to tracks · all time
Total agents in agenteconomy.to’s ERC-8004 table, on the chains it tracks.
read 2026-10-24 · source date 2026-10-23T02:26:40.963Z
Our own reading is the registry contract's own id counter on each chain, read directly and never summed. ERC-8004 agents by chain →
Figures other trackers publish, quoted with their source and read once a day. They are not Sato Hub's numbers and are never added together; “not read” means we hold no reading, never zero.
Data CC-BY-4.0 — attribution: data by satohub.ai. Never summed across chains; unknown means the read failed that week, never zero.
Reference
Cite this pagePlain text, APA or BibTeXShowHide
Cite this
As of 2026-10-19, registered ERC-8004 agent ids per chain, never summed: BNB Chain 376,540 (+4,347 on the week), Base 271,519 (+165,403 on the week), Ethereum 54,306 (+1,600 on the week) and 7 more chains.
Sato Hub, "How is the ERC-8004 registered-agent count trending on each chain?", https://satohub.ai/numbers/erc-8004-registered-agents, as of 2026-10-19. Data CC-BY.
How this was measured
- Method
- The ERC-8004 Identity Registry's own agent-id counter (`_lastId`, one storage read at the chain head), read once a week on each chain and compared with the previous week's reading, covering the whole registry with no sampling.
- Window
- One reading per chain per week, set against the week before.
- Data date
- MCP call
onchain_agent_get_trend({"venue":"erc8004","chain":"Base","stage":"registered","grain":"weekly","points":12})on https://satohub.ai/api/mcp- URL
- https://satohub.ai/api/export/adoption.json?stage=registered&venue=erc8004
The export carries the current week only; the MCP call returns the series. Pass another chain for its series; chains are never blended.
Machine source
- JSON export: https://satohub.ai/api/export/adoption.json → rows where venue="erc8004" and stage="registered" (current week)
- MCP tool: https://satohub.ai/api/mcp → onchain_agent_get_trend({ venue: "erc8004", stage: "registered", chain: "BNB Chain", grain: "weekly", points: 12 })