ERC-8004 implementation
ERC-8004 gives agents portable on-chain identity and reputation; we implemented the standard end to end and run it on two public testnets.
The problem
Machine-to-machine commerce has an identity problem before it has a payment problem: who is this agent, who runs it, and has it behaved? Platform accounts answer that inside one walled garden. The moment agents from different operators transact, trust needs a substrate none of them owns.
ERC-8004 is that substrate - identity and reputation registries on a public chain. The standard is young enough that implementation experience is scarce; ours comes from building Azeth, where registration, discovery, and payment-gated reputation run against the registries on two testnets, at addresses anyone can inspect.
Engagement
Fixed-scope implementation: we map your trust model onto the standard (who registers, who may rate whom, what gates a rating), deploy or integrate the registries, and deliver the indexer and query layer your product actually consumes. Testnet-first, with explicit criteria for anything that moves toward mainnet.
Start by email: what to include is on the contact page.
What we ship
- Registry contract deployment or integration with the canonical registries
- Identity registration flows for your agents and services
- Reputation writes gated by verified payments, not free-for-all reviews
- Indexing and a query API your applications can consume
- Explorer or dashboard surfaces for human inspection
Proof
- Azeth: trust infrastructure shipped to two testnetsCase study
- AzethPortfolio entry · testnet alpha
Common questions
What is ERC-8004?
An Ethereum standard for agent trust: an identity registry that gives an agent a stable on-chain handle, and a reputation registry that records assessments about it. The point is portability - trust that lives on a public chain instead of inside one platform's database.
Why put agent identity on-chain at all?
Because the parties who need to check it do not share a database. An agent hiring another agent needs an identity and a track record that no single vendor controls and no counterparty can quietly edit. A public registry is the neutral ground.
How does payment-gated reputation work?
A reputation entry carries weight only when the rater verifiably paid for the rated service - in our implementation, via x402 receipts. It does not make dishonesty impossible; it makes it cost money, which removes the free spam that drowns most review systems.
Is the standard final? What if it changes?
It is an emerging standard, and we treat that honestly: our deployments version the integration layer so registry changes stay behind one interface. What we run today is on Ethereum Sepolia and Base Sepolia - verifiable on-chain, linked from our /open page.
Can this run on our own chain or L2?
The contracts are portable to EVM-compatible chains. Whether a private deployment is useful depends on who must trust the registry - a members-only chain answers differently than a public one, and we will tell you which your case needs.
Industries
last edited 2026-07-02