Axiom One

Field note · ERC-8004

What does ERC-8004 add to agent commerce?

A job protocol can move work and money. ERC-8004 addresses a different question: which agent is this, what reputation signals exist, and who validated the result?

Read the draft standardExplore GEO
Current status

Draft standards-track ERC. Useful for architecture and experiments, but still subject to change.

The gap

What problem does ERC-8004 solve?

Agent protocols can advertise skills, exchange messages, negotiate work, and settle a job. Those mechanics do not by themselves establish portable identity or trustworthy evidence across organisations.

ERC-8004 proposes three lightweight on-chain registries for that trust layer.

IdentityA portable agent identifier linked to a registration file.
ReputationStandard signals for feedback, with scoring left to competing systems.
ValidationRequests and results from independent validation methods.

The boundary

What does registration not prove?

An on-chain identity proves that a registry entry and its controller exist. It does not prove that the advertised service works, that its output is safe, or that its operator will fulfil a job correctly.

The draft also leaves payments outside its scope. A payment or escrow protocol can sit beside ERC-8004, but the registry does not replace that commerce rail.

Registration gives an agent a coordinate. Trust still requires evidence.

Protocol fit

How does ERC-8004 fit Virtuals ACP?

Virtuals Agent Commerce Protocol covers discovery, requirements, jobs, funding, delivery, evaluation, and completion. ERC-8004 can add a portable identity plus reputation and validation records around those outcomes.

The useful separation is simple: ACP runs the commercial job; ERC-8004 carries trust signals that other systems may inspect.

Read the Virtuals ACP architecture

Buyer check

What should a buyer verify today?

  1. The canonical registry, chain, and agent identifier.
  2. The registration URI, controller wallet, and declared endpoints.
  3. Whether the advertised service is reachable and matches the listing.
  4. Who issued each reputation signal and how it was calculated.
  5. What a validator actually checked, against which evidence and version.
  6. Which separate protocol handles payment, escrow, approval, and disputes.

Axiom One view

Where does authority review still matter?

Open registries make evidence easier to locate and reuse. They do not decide how much an agent may spend, which tools it may call, when a human must approve, or whether one specific deliverable meets the agreed conditions.

That is the remaining control problem: connect identity and reputation to a bounded action, a named evaluator, and a receipt that survives the job.

Primary sourcesERC-8004: Trustless Agents, current draftVirtuals Agent Commerce Protocol architecture

Turn a registry signal into a real launch decision.

We review one agent flow, its authority boundary, evidence, evaluator path, and acceptance conditions.

Discuss one flow