← Home · Data hub · Ethereum chain brief · Base chain brief

Canonical live answer · verified 2026-09-01

Which chains is ERC-8004 actually deployed on?

Per-chain deployment table verified at 2026-09-01. Indexed counts refresh live on every visit; deployment facts are re-verified at source, not from a search snippet.

Short answer: ERC-8004 is deployed and reachable on four chains today — Ethereum and Base (both on the CREATE2 IdentityRegistry at 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432), BNB Chain (on the same address plus the BRC8004 BNB-team fork at 0xfA09B3397fAC75424422C4D28b1729E3D4f659D7), and Solana via the QuantuLabs 8004-solana port (deployed 2026-03-04). Arbitrum is NOT deployed as of 2026-09-01: the Arbitrum Foundation blog describes the standard as “still under review” and provides no contract address. The widely-circulated “15 chains” list including Celo, HyperEVM, Ink, Optimism, Plasma, Polygon, Ronin, Sonic, Unichain, Worldchain did not reproduce at its cited source when we fetched it on 2026-09-01.

Per-chain deployment table

Chain Registry deployed? How we verified Do we index it?
Ethereum Yes0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 eth_getLogs on the IdentityRegistry (Transfer(from=0x0)), full census. Yes2,827 indexed after per-publisher dedup. /chains/ethereum
Base Yes0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 (same CREATE2 address) eth_getLogs on the IdentityRegistry, full census. Yes22,914 indexed after per-publisher dedup. /chains/base
BNB Chain Yes0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 plus the BRC8004 BNB-team fork at 0xfA09B3397fAC75424422C4D28b1729E3D4f659D7 eth_getLogs on both registries via erc8004_discovery.py --chain bnb. Scanned, not served. The served hubs are Base + Ethereum only per task 0215's all-Ethereum posture — BNB live rate at the time of the cut was too low to justify a served hub.
Solana (QuantuLabs port) Yes — mainnet, deployed 2026-03-04. Agent-registry program: 8oo4dC4JvBLwy5tGgiH3WwK4B9PWxL9Z4XjA2jzkQMbQ. Atom-engine program: AToMw53aiPQ8j7iHVb4fGt6nzUNxUhcPc3tbPBZuzVVb. Devnet also live with distinct program IDs. Verified at source via github.com/QuantuLabs/8004-solana on 2026-09-01. The README claims no adoption count — a good sign; population-scale claims from other sources have not held up when we fetched them. No. This is a known gap in our coverage. Indexing Solana would require a Solana RPC quota and a discovery loop distinct from the EVM eth_getLogs pattern our existing three chains use.
Arbitrum No — not deployed as of 2026-09-01. Verified at the Arbitrum Foundation blog on 2026-09-01: the post describes the standard as “still under review” and provides no contract address and no Arbiscan link. The upstream snippet asserting “live on Ethereum, Base, Polygon, Arbitrum” did not reproduce at source. N/A — nothing to index.
Celo, HyperEVM, Ink, Optimism, Plasma, Polygon, Ronin, Sonic, Unichain, Worldchain Unverified. Named in a widely-repeated “15 chains” list. Cited source (payram.com) fetched on 2026-09-01: the page uses Arbitrum as a “potential deployment location” example only and does not list contract addresses for these chains. Claim did not reproduce at source. Recorded UNVERIFIED in the signpost-gap discussion and in docs/evidence/0375-ecosystem-opportunity-scan.md §5. N/A — deployment not established.

Where the “15 chains” claim came from

The specific list — Ethereum, Optimism, Base, Arbitrum, HyperEVM, Plasma, Polygon, Ronin, Unichain, Ink, Celo, Solana, Sonic, BSC, Worldchain — circulates in secondary explainers and search snippets. On 2026-09-01 we fetched the cited primary sources and could not reproduce the claim:

This is a correction, not an accusation: snippets get republished, and a widely-quoted list stays quoted long after its source has been superseded. The point of this page is to give a single re-verified table anyone can cite instead.

Method

Registry addresses. The ERC-8004 IdentityRegistry uses the same CREATE2 address on every EVM chain where it is deployed (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Presence on a chain is established by confirming that address is a deployed contract with Transfer(from=0x0) event history via eth_getLogs. BNB additionally carries a BNB-team fork, BRC8004, at 0xfA09B3397fAC75424422C4D28b1729E3D4f659D7; both are scanned by erc8004_discovery.py.

Solana (QuantuLabs 8004-solana). Not the same registry — Solana requires Solana-shaped program-derived-address (PDA) accounts rather than EVM contracts, so the QuantuLabs port is a distinct implementation of the ERC-8004 concept on Solana runtime. Verified at github.com/QuantuLabs/8004-solana: README publishes mainnet program IDs for agent-registry (8oo4dC4JvBLwy5tGgiH3WwK4B9PWxL9Z4XjA2jzkQMbQ) and atom-engine (AToMw53aiPQ8j7iHVb4fGt6nzUNxUhcPc3tbPBZuzVVb) and separate devnet program IDs, with a deployment date of 2026-03-04.

Arbitrum (not deployed). Verified by fetching the Arbitrum Foundation's own blog on ERC-8004 at blog.arbitrum.foundation on 2026-09-01. Absence of a contract address on the standards-team's own page is the strongest available evidence of not-yet-deployed.

Source-fetch record. Full URL list, fetch dates, and snippet-vs-source disagreements are recorded in docs/evidence/0375-ecosystem-opportunity-scan.md §2c and §5. Every unverified chain listed above is marked SNIPPET-ONLY — UNVERIFIED in that record.

ERC-8004 v2. No v2 of the specification exists today (verified 2026-08-31, re-verified 2026-09-01). The EIP remains at Draft status. Third-party claims of “richer on-chain reputation primitives in v2” are not sourced to the EIP repo.

Limitations

Cite this answer

Scoped claim sentence. Scope: ERC-8004 IdentityRegistry deployment status verified at 2026-09-01 — Ethereum, Base, and BNB Chain deployments confirmed at 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 (BNB also carries the BRC8004 fork at 0xfA09B3397fAC75424422C4D28b1729E3D4f659D7); Solana via QuantuLabs 8004-solana confirmed at https://github.com/QuantuLabs/8004-solana; Arbitrum confirmed not deployed at https://blog.arbitrum.foundation/ai-on-arbitrum-establishing-an-agent-registry-with-erc-8004-2/.

License. Answer prose and every rendered number published under CC BY 4.0 — free to reuse, including in commercial work, provided you attribute “On-Chain Agent Intel” and link back to https://onchainagentintel.io/erc-8004-chain-deployment-status.

Machine-readable source. Per-chain indexed counts are a live projection of /v1/public/stats.

Also useful: How many agents? · How many x402 endpoints are actually used? · Can you trust an ERC-8004 reputation score? · How do you know which agent is safe to pay? · Chain-liveness dataset · All datasets