ERC-8004 registry partner guide

Register a deployment

Provide the canonical network, registry contracts, deployment key/version, start block, finality policy, explorer templates, ABI/event signatures, and authoritative documentation links. Configuration is validated and activated as a versioned indexer target; credentials and RPC URLs remain secret references.

{
  "protocol": "erc8004",
  "network": "eip155:8453",
  "deploymentKey": "erc8004-base",
  "startBlock": "12345678",
  "finality": { "confirmations": 12 }
}

The bootstrap smoke test must ingest representative identity, reputation, and validation observations, persist source hashes and block/log identity, materialize canonical projections, and survive replay without duplication.

Evidence rules

Registration documents are fetched through bounded SSRF-safe adapters. Preserve raw bytes/hash, URI, media/encoding, parser version, fetch time, and errors. Chain reorg reconciliation changes canonicality and rebuilds dependent projections; it never destroys observations.

Identity/reputation/validation remain separate schemas. A registry entry does not imply verification, and feedback does not imply ownership. Partner UI links to the protocol hub and exact public identity/entity resources.

Operations

Monitor target lag, finalized checkpoint, RPC/provider circuit, dead letters, parser failures, and projection consistency. Credential rotation overlaps references and verifies new credentials before retirement. Reindex and replay plans require bounded ranges, dry-run preview, audit reason, and idempotent execution.