ERC-8004 Identity Registry integration

[lthibault]

A Wetware node registers itself on the ERC-8004 Identity Registry (ERC-721 based). The agent registration file (JSON) points to the node's libp2p multiaddr and MCP endpoint. NFT ownership = agent ownership.

Ref: https://eips.ethereum.org/EIPS/eip-8004

Acceptance criteria

• Wetware-hosted agent is discoverable via the ERC-8004 registry
• Registration file includes libp2p multiaddr and MCP endpoint
• Agent identity is portable (transferred via NFT)

[douglasborthwick-crypto]

For the "agent identity is portable (transferred via NFT)" acceptance criterion — third-party verification of that NFT ownership is the trust anchor.

InsumerAPI verifies ERC-721/ERC-8004 NFT ownership across 31 EVM chains and returns an ECDSA-signed boolean. When a Wetware node claims identity via its ERC-8004 registration, any consuming agent can verify:

POST /v1/attest
{
  "wallet": "0xNODE_WALLET",
  "chain": "base",
  "contract": "ERC_8004_REGISTRY",
  "condition": { "minBalance": "1" }
}
→ { "holds": true, "sig": "ECDSA-P256", "kid": "insumer-attest-v1" }

When the NFT transfers (identity portability), the next attestation call for the old wallet returns holds: false and for the new wallet returns holds: true — no state to manage.

Since you're already exposing MCP endpoints, there's an MCP server (mcp-server-insumer on npm) that wraps these verification tools — an agent discovering your node via MCP could also discover the verification tool through the same protocol. API spec: https://insumermodel.com/openapi.yaml