Rightshold Sign up

ERC-8004 bridge

ERC-8004 identities, read as evidence

The ERC-8004 bridge resolves an agent registered in the ERC-8004 (EIP-8004 Trustless Agents) Identity Registry into one evidence document: the on-chain facts (the token owner and the agentURI, read at a named block height from the chain's registry contract), the registration file the agentURI points to — the agent's own declarations, labeled as claims and text-scanned at ingestion — and the Reputation Registry's published counts for the agent, shown with their registry address and sample size. An ERC-8004 identity resolved here is not a Rightshold KYA registration: no RS registration number is issued or implied, and nothing on this page is a grade, a score of Rightshold's own, or a finding about the agent. Rightshold reads these registries; in this release it writes nothing to them.

Reads are live chain reads, cached for seconds and labeled with the block height they were read at. A token with no owner on the named chain answers 404; an unreachable or disagreeing set of RPC endpoints answers 502 naming the chain, never a fabricated empty record.

Chains read

Resolve one

curl -s "https://www.rightshold.com/v1/erc8004"

That index names the resolve form, GET /v1/erc8004/{chain_id}/{agent_id} — agent 1 on Sepolia shows the shape. The same document is the agent's one-lookup import: GET /v1/identity/eip155-11155111-1, with its evidence page at /identity/eip155-11155111-1.

The write half

Rightshold posts nothing into the ERC-8004 registries in this release: posting is a signed on-chain act that waits on the owner's decision, a named Sepolia-first wallet and a key-custody record. The deterministic value mapping that posting would follow is published in the index document (GET /v1/erc8004) so it can be read before it is ever used.