Here's what Ethereum’s agent identity standard actually solves, what it deliberately leaves open, and why that matters for anyone building trust infrastructure.
ERC-8004 launched on mainnet on January 29, 2026. 40K+ agents landed on Base in under two weeks. Audited by Cyfrin and Nethermind. It's solid work, but there's a gap between what developers assume it does and what contracts actually execute.
What ERC-8004 solves: Infrastructure Primitives
ERC-8004 is a set of three on-chain registries. It’s a library of storage primitives, not a decision engine:
- IdentityRegistry: Mints ERC-721 NFT per agent. Provides on-chain proof of existence.
- ReputationRegistry: Stores raw feedback signals. Anyone can call giveFeedback().
- ValidationRegistry: Independent pass/fail responses for specific capabilities.
This is the right design for a base-layer standard: do one thing (storage), do it on-chain, and let ecosystem handle logic.
8 Gaps (Deliberate by Design)
If you're building on ERC-8004, realize what standard doesn't handle:
- No reputation aggregation: It stores raw data. There is no "final score". One indexer might see 0.9 agent, while another might see 0.3.
- Zero Sybil resistance: giveFeedback() is open. You can spin up 100 wallets and self-attest to glory. Contracts won't stop you.
- Immutable noise: On-chain data is permanent. Unfair negative feedback stays in history even if "revoked".
- Identity != Trust: Mints are cheap. Registry full of 40K agents tells you nothing about which 10 are actually legitimate.
- No Dispute Resolution: You can post response to feedback, but there’s no path to arbitration or escrow.
Why this matters: Primitives need Compute
DNS stores records, but doesn't tell you if domain is phishing. SMTP delivers mail, but doesn't filter spam.
Storage primitives need compute layers.
ERC-8004 needs an "Aggregation & Enforcement" layer that a single operator doesn't control. If any single indexer controls scoring algorithm centrally, we've just traded one gatekeeper for another.
Our Approach: Agent Veil Protocol (AVP)
We’re building AVP as an off-chain compute layer for this ecosystem. We take ERC-8004 raw data and run it through EigenTrust — graph-based algorithm that powered early, non-gameable web trust.
ERC-8004 Raw Feedback -> AVP EigenTrust Compute -> Verified Trust Score
+ Sybil Cluster Analysis
+ Collusion Detection
+ Dispute Resolution
AVP is decision engine. ERC-8004 is settlement layer.
By using EigenTrust, scores emerge from structure of attestation graph itself. If cluster of 50 agents all vouch for each other but have no outside trust, their impact on global score is mathematically zero.
Bottom line
ERC-8004 is great infrastructure. But don't mistake registry for trust system. Scoring that matters is scoring you can't buy or game.
Try bridge:
GET https://agentveil.dev/v1/bridge/erc8004/{did}/attestation
Open Source SDK: github.com/creatorrmode-lead/avp-sdk
pip install agentveil
Top comments (0)