Where the ERC-8004 registrations live, chain by chain

The reference registry sits at one address on every chain, so it can be read everywhere with the same two calls. Read from public nodes on 40 EVM chains: 5,577,152 registrations in all, 3,940,750 of them on 0G from one platform, 3.5 times Base. No public tracker counts 0G. A registration is a token, not an agent.

Agentic Finance Graph · Measured 2026-10-24 09:24 UTC · Definition reg.chains.upperbound.v1 · Snapshot SHA-256 1896bcf6799f4823… · Licence CC BY 4.0

The claim, in one sentenceCounting ERC-8004 registrations chain by chain, 0G holds more than Base (3,940,750 against 1,123,064), almost every large registry outside Base is one platform's minting wave, and the figures public trackers publish leave the largest chain out.

Method, so that anyone can repeat it

One address everywhere. The reference Identity Registry is deployed by CREATE2 at 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on every chain. eth_getCode says whether it is there.
Sequential ids. Agent ids start at 1 and rise by one per registration, so ownerOf(id) answers for every minted id and reverts above the last one. A binary search over ownerOf finds the highest existing id in about 25 calls. That id is an upper bound on registrations minted: a burn leaves a gap below it, and an exact count needs the Transfer-from-zero logs.
Who minted. Twelve tokenURI reads spread over each chain's id range name the host behind the registrations, and the twelve ownerOf answers say how many distinct owners sit among them.
Two ways. Where a second, unrelated public endpoint is configured, it re-reads the boundary (the highest id exists, the next does not). On this snapshot 17 of 17 agreed.
Public nodes only, no provider key, under a minute for 40 chains, once a day (afg-regchains). The daily document is /api/registry-chains.

The registries, chain by chain

Every EVM chain where the reference registry holds registrations, 2026-10-24 09:24 UTC
Chain	Highest agent id	Second endpoint	Dominant agentURI host (share of 12)	Owners among 12	In our census
0G (16661)	3,940,750	agrees	metadata.evoevo.ai (100%)	12	no
Base (8453)	1,123,064	agrees	centralcity.ai (83%)	12	yes
BNB Smart Chain (56)	382,289	agrees	inline metadata (50%)	12	yes
Ethereum (1)	55,332	agrees	empty URI (33%)	9	yes
Abstract (2741)	16,918	agrees	cryptomazeapp.fra1.digitaloceanspaces.com (92%)	12	no
xlayer (196)	15,137	agrees	static.okx.com (100%)	12	no
MegaETH (4326)	12,727	agrees	8004glyphs.vercel.app (58%)	12	no
Monad (143)	10,417	no answer	eve-8004.vercel.app (75%)	12	no
Celo (42220)	9,987	no answer	inline metadata (83%)	5	no
Gnosis (100)	4,168	agrees	marketplace.olas.network (92%)	2	no
Avalanche C-Chain (43114)	1,846	agrees	empty URI (83%)	3	no
Arbitrum One (42161)	1,641	agrees	ipfs (67%)	11	yes
Injective EVM (1776)	931	not configured	ipfs (91%)	5	no
Polygon PoS (137)	690	agrees	empty URI (25%)	10	yes
OP Mainnet (10)	567	agrees	inline metadata (50%)	5	yes
Mantle (5000)	145	agrees	inline metadata (75%)	6	no
Metis (1088)	138	agrees	inline metadata (92%)	2	no
Linea (59144)	116	agrees	unparsable URI (83%)	3	no
Scroll (534352)	109	agrees	unparsable URI (92%)	2	no
Taiko (167000)	93	agrees	ipfs (100%)	4	no
goat (2345)	87	not configured	inline metadata (42%)	10	no

Registry deployed but empty on Flow EVM, HyperEVM, Ink, Soneium. No registry code on Berachain, Blast, Cronos, Fantom, Mode, Plasma, Sei EVM, Sonic, Story, Unichain, World Chain, zkSync Era, Zora. Endpoint down or refusing on the day: Moonbeam, Ronin (never written as zero). Our own census reads Base, BNB Smart Chain, Ethereum, Arbitrum, OP Mainnet, Polygon and Solana; the chains marked "no" are in no figure of ours except this one.

Two figures

The four largest registries, highest existing agent id, 2026-10-24 09:24 UTC. Together 5,501,435.

The fifteen smaller registries, same measure. Together 75,537.

What the numbers say, and what they do not

0G: 3,940,750 registrations, one platform. Every sampled agentURI from the first id to the last resolves under metadata.evoevo.ai, with a distinct owner address per sampled id. The same platform also mints on BNB Smart Chain. Whether these are agents, accounts or passports is the question we already ask about Central City on Base, whose host answers 83% of Base's sample: the registry counts tokens.
The pattern repeats on every large registry outside Base: Abstract (cryptomazeapp.fra1.digitaloceanspaces.com, 12 owners among 12); xlayer (static.okx.com, 12 owners among 12); MegaETH (8004glyphs.vercel.app, 12 owners among 12); Monad (eve-8004.vercel.app, 12 owners among 12); Celo (inline metadata, 5 owners among 12). Registrations per chain measure how one platform used the registry there, not adoption by independent operators.
No public tracker counts 0G. On 23 October 2026, 8004scan reported 1,856,049 registrations in total and agenteconomy.to 1,333,878; Base and BNB alone are 1,505,353, and Base plus 0G 5,063,814. Any "ERC-8004 registrations" figure should say which chains are inside it. Ours do: erc8004_registrations_census_all covers the seven chains we read, as its producer label says.
What this does not assert: that a registration is an agent; that a platform wave is wrong or empty (the registry is designed to be used by platforms); that the upper bound is an exact count; anything about the people behind any address.

Why it matters for an accounting of agent money

A ledger of agents' money needs a denominator. If the denominator is "registrations", the choice of chains changes it by a factor of five, and one platform's wave on one chain moves it more than every independent operator combined. That is why we rank by behaviour seen on chain (L7 seen paying, L8 still funded, L9 with three counterparties) rather than by registrations, and why every registrations figure of ours carries its chain list and, from today, the platform shares behind it.

Verify this finding

The snapshot. Every figure on this page comes from where-erc-8004-registrations-live-chain-by-chain.json; its SHA-256 is 1896bcf6799f48238f8dd972fbbbb3c58ef67b3de935a7dc13e96512c88fc957. The live document is /api/registry-chains, re-read daily.
Two calls, any node. eth_getCode on 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432, then eth_call with data 0x6352211e + the id as a 32-byte word (ownerOf); 0xc87b56dd + the id gives tokenURI. No key, no account.
The definition. reg.chains.upperbound.v1, frozen; a change of method is a new version and a dated entry in the register.
The PDF. The same finding as a paper: afg-finding-where-erc-8004-registrations-live-chain-by-chain-2026-10-24.pdf.
Independence. Agentic Finance Graph has no token; AFG and its operator hold no position in the tokens discussed; nobody pays for a level, a rank or a placement; a finding is public before any paid depth of it is sold (stated 24 October 2026).