Sato Hub
← Back to blogERC-8004 just passed 35,000 registrations — here's what that number actually counts

ERC-8004 just passed 35,000 registrations — here's what that number actually counts

The on-chain agent-identity registry is real and verifiable. It's also a mint counter, not a population census — and the difference is the whole point.

2026-06-24 · 4 min read

Agents that hold a wallet and act onchain need one thing a chatbot never did: a way to be *recognized* across services they've never met. As of this writing, ERC-8004's Identity Registry on Ethereum mainnet has logged 35,367 registrations — a number we read directly from the contract's storage, not from a press release. It's real, it's on-chain, and it's a genuinely useful signal that the agent-identity layer has shipped and is being used.

It's also being widely misread. "35,000 agents registered" is getting passed around as if it were a census of living, working agents. It isn't. It's a counter. Here's exactly what it counts, why that matters, and what to actually watch.

What ERC-8004 is

ERC-8004, titled ["Trustless Agents,"](https://eips.ethereum.org/EIPS/eip-8004) is an Ethereum standard for letting agents "discover, choose, and interact with agents across organizational boundaries without pre-existing trust." Translation: it's plumbing so an agent built by one team can verify and transact with an agent built by another, without a shared platform vouching for either.

It defines three on-chain registries:

  • Identity Registry — an ERC-721 contract giving each agent a portable, censorship-resistant identifier that resolves to a registration file (endpoints, capabilities). This is the one with 35,367 entries.
  • Reputation Registry — a standard interface for posting and reading feedback signals about an agent's performance, scored on-chain with the heavy aggregation left off-chain.
  • Validation Registry — where an agent can request independent verification of its work through validator contracts: stake-secured re-execution, zero-knowledge proofs, or trusted-execution-environment oracles.

A detail for the address-watchers: both live contracts carry a vanity prefix — Identity at [0x8004A1…](https://etherscan.io/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432), Reputation at [0x8004BA…](https://etherscan.io/address/0x8004BAa17C55a88189AE136b182e5fdA19dE9b63). On-brand for a standard numbered 8004.

What "35,367" actually measures

The Identity Registry mints an ERC-721 token per registration and hands each a sequential id from an internal counter. That counter — not a live headcount of distinct, active agents — is the number everyone's quoting. It only ever goes up. It counts how many times anyone has called register() since the contract went live, full stop.

Three things that counter does not tell you:

1. How many distinct operators are behind it. One team can register a hundred agents in an afternoon; total registrations and unique holders are different metrics, and the holder count is the smaller one. 2. How many are still doing anything. Registration is a one-time mint. Nothing in that number says an agent ran today, last week, or ever. 3. Whether any of them are any good. Registering an identity is not the same as having earned reputation or passed validation — those live in the *other two* registries, which is rather the point of splitting them up.

So when a writeup turns the counter into "35,000 AI agents are now live on Ethereum," it's quietly swapping a mint counter for a population census. The standard's own authors didn't make that claim; the hype cycle did.

Why it still matters

None of that makes the number boring — it makes it *honest*. An identity layer is supposed to be cheap to join and permissionless; a low bar to entry is a feature, not a bug. What ERC-8004 gets right is the separation of concerns: identity is one registry, reputation is another, verification is a third. You register first and *earn* the rest.

That maps cleanly onto how we think about trust at SatoHub. An ERC-8004 registration is an identity signal — portable, on-chain, real. It is explicitly not a quality, safety, or returns grade, and anyone reading it as one is reading it wrong. Identity is the floor. Reputation and validation are the building. The whole architecture is an argument that you shouldn't conflate the two — the same argument we make every time someone calls a self-reported listing "verified."

What to watch

The registration counter will keep climbing; that's the least interesting number on the board now. The real tells for whether onchain-agent identity is working:

  • Does the Reputation Registry fill in? Feedback signals accumulating on-chain is the difference between "35,000 names" and "a working reputation graph."
  • Does the Validation Registry get used? Stake-secured re-execution and ZK/TEE attestations are where "trustless" stops being a slogan. Adoption there is the signal that matters.
  • Do registrations convert to activity? Watch the gap between total registrations and agents that actually transact. A narrowing gap means real adoption; a widening one means a lot of cheap mints.

ERC-8004 shipping and getting used is good news for everyone building onchain agents — including us, since identity is the layer everything else sits on. Just hold the number at the right altitude: 35,367 agents have a verifiable on-chain *name*. How many have earned a verifiable *reputation* is the question the next year answers.

We read the live count straight from mainnet on [SatoHub's ERC-8004 page](https://satohub.ai/resources/erc-8004) — on-chain, not self-reported. Go check our math.

Sources

Join the Sato Hub Briefing

One email a week — the agents, tools, and infrastructure that actually shipped, and why they matter.