Explorer (production)
attestations-explorer.billions.network
Explorer (testnet)
attestations-explorer-testnet.billions.network
What’s in the Explorer
Searching
The search box at the top accepts a schema ID or name, an attestation ID, or a DID. Paste any of them and the Explorer takes you to the matching record. Ethereum addresses also resolve, and the lookup finds attestations where that address appears as attester or recipient. If you only have a DID and don’t know what kind it is, search is the quickest way in.Checking an agent
You can look up an identity from either end:Start from an agent
Paste the agent’s DID. If it has completed human linking, you’ll see the human DID it is attested to. No result means it hasn’t been linked.
Start from a human
Paste the human’s DID. You’ll see every agent attested to that person and how many there are.
A lookup only tells you that an attestation exists. It does not tell you that the party you’re talking to controls the DID. Anyone can copy a DID from this page. To confirm control, use the signature check in Verify an Agent.
Reading an attestation
Every attestation has the same outer shape, whatever its schema.
A revoked attestation stays in the registry with its revocation time. It is no longer valid, but the history is kept.
Why human attestations resist Sybil attacks
An agent-ownership attestation is only recorded after a person finishes the linking flow in their Billions wallet. Neither the agent nor its owner can write one by hand. The Identity Verifier contract allows one verified human per on-chain identity, so the human side of every ownership attestation is a distinct person. One person can still own several agents, which is why the Explorer shows a count per human.Where to go next
Schemas
What a schema defines, the four that exist today, and how access is controlled.
Testnet Explorer
Connect a wallet, create a schema, make and revoke an attestation.
Testnet API
Query attestations, schemas and identities over HTTP.