ERC-8126: AI Agent Verification

ERCs
, ,
21

@Cybercentry makes sense to keep Last Call closed and address these via a companion vehicle. That’s cleaner than reopening.

On the serialization flexibility in the previous post, agreed, the flexibility is the right design choice for the main spec. The consumer-side discovery gap is the actual problem, not the flexibility itself. What breaks isn’t the serialization options existing.

It’s that a verifier has no deterministic way to know which format it’s looking at without probing. A carrierFormat field (or a discovery header convention) would close that without constraining provider choices at all — pure additive.

On the tokenURI schema gap in latest post — ENSIP-27 is positioned exactly to be that companion. It defines what tokenURI returns for ERC-8004 registered agents (walletAddress, endpoints, registrations in CAIP-19 format), so ERC-8126 verifiers have a deterministic extraction path without guessing field names. If the follow-up vehicle cites ENSIP-27 as the normative schema, the gap closes.

ENSIP-27 PR is at review stage now: https://github.com/ensdomains/ensips/pull/75

Happy to contribute to the companion ERC draft if there’s a thread or working doc.

22

Hi TMerlini,

A clarification: ERC-8004 does specify the registration file schema returned via tokenURI (type, name, description, services, registrations, supportedTrust, etc.), with wallet resolution canonical via getAgentWallet(agentId). So those paths aren’t undefined in 8004.

That said, 8126’s text references field names that sit outside that base schema, fair point, and a coherence item for the follow-up vehicle.

Specific schema choices belong in the follow-up, not Last Call.

Thanks,
Leigh
@cybercentry
cybercentry.base.eth

1 Like
23

Hi TMerlini,

Agreed on Last Call disposition.

The companion vehicle isn’t scoped yet. When it is, the discussion thread will be public; schema choices and normative references, ENSIP-27 included, will be evaluated on their merits during that scoping. I don’t want to pre-commit to any specific external schema or field convention before the work begins.

Will share the thread once it’s up.

Thanks,
Leigh
@cybercentry
cybercentry.base.eth

1 Like