Skip to main content

​
The Linking Flow

1

Agent creates its DID

The agent generates its own DID locally using the iden3 protocol, an open-source ZK identity framework that derives cryptographic identifiers from key pairs. Nothing goes on-chain at this point.
2

Agent shares a verification link

When asked to link its identity, the agent generates a verification link scoped to this specific human-agent pairing and shares it with the human owner.
3

Human verifies ownership in the Billions Web Wallet

The human opens the link in the Billions Web Wallet. If they haven’t already claimed a Proof of Uniqueness credential, the claim process (a one-time face scan) starts automatically; if they have, it’s reused. Either way, the wallet generates a zero-knowledge Proof of Uniqueness and an auth proof, and submits them to the Relay Attestation Service.
4

Permanent attestation created on-chain

The Relay makes two on-chain calls on the Billions Network. First, the Identity Verifier Contract verifies the ZK proof and stores it against the user’s DID, enforcing PoU’s one-human-one-identity guarantee. Then, the Attestation Registry Contract creates a permanent on-chain attestation linking the verified human to the agent’s DID.
The resulting attestation is on-chain and queryable by any third party to confirm agent ownership.

​
Architecture

Five components carry the flow from a locally generated key pair to a public on-chain attestation: Reading the diagram in flow order:
  1. Verified Agent Identity skill: runs on the agent. It derives the agent’s DID from a local key pair and orchestrates the linking flow, starting by sending the human owner a verification link.
  2. Billions Web Wallet: where the human proves who they are. It generates a zero-knowledge Proof of Uniqueness (proving the human is real and unique without revealing personal data) plus an auth proof, and submits both.
  3. Relay Attestation Service: the off-chain bridge. It receives the proofs and turns them into two on-chain transactions.
  4. Identity Verifier Contract: verifies the ZK proof on-chain and stores it against the human’s DID. It’s Sybil-resistant by design — one verified human maps to exactly one on-chain identity, so a single person can’t register more than once.
  5. Attestation Registry Contract: writes the permanent, public attestation linking the verified human’s identity to the agent’s DID.

​
Demo

This demo shows the full flow end to end: an agent going from no identity to an on-chain pairing with its human owner, in a few minutes.
The demo uses Billy, an agentic bot on Telegram, built with the OpenClaw framework for building and deploying AI agents. The demo follows Billy through exactly the flow described in The Linking Flow above. A few details worth watching for:
  • Installation takes a single chat message.
  • The face scan happens only once: first-time users claim a Proof of Uniqueness credential in the Billions Web Wallet with a one-time scan, then the same credential is reused for every future verification.
  • The result is checkable end to end. Billy appears under Verified Agents in the user’s wallet profile, and the last four characters of his DID (V9HT) match what he shared in the Telegram chat.

​
Under the Hood

Everything above happens automatically. The sections below document exactly what the skill does on disk and on-chain, for when you need the details.
When installed, the skill adds a scripts/ directory to the agent’s workspace and runs npm install to set up dependencies.All cryptographic material is stored in $HOME/.openclaw/billions/ (OpenClaw’s data directory), outside the agent’s workspace, so identity data persists across sessions and agent restarts. The agent reads this directory on startup to load its default DID and private keys.When the agent receives a natural-language trigger (e.g. “link your identity to me”), the skill’s instruction set maps it to the appropriate script, executes it as a subprocess, and returns the result to the conversation.
When the human clicks the verification link, the Billions Web Wallet initiates the following sequence:
  1. Auth proof: a JWS token is generated, signed with the agent’s private key, proving DID ownership.
  2. Proof of Uniqueness: a ZK proof is generated in the wallet, proving the human is a real, unique individual without revealing personal data.
  3. Both proofs are submitted to the Relay Attestation Service.
  4. The Relay calls the Identity Verifier Contract on the Billions Network, which verifies the ZK proof on-chain and stores it against the user’s DID — the same one-human-one-identity guarantee described above.
  5. The Relay calls the Attestation Registry Contract (ERC-8004, a standard for on-chain attestation registries). A permanent on-chain attestation is written linking the verified human’s DID to the agent’s DID.
The attestation is public and immutable — any third party can query it to confirm agent ownership.

​
Next Steps

Installation

Install the skill and link your agent’s identity to you in two chat messages.

Verify an Agent

Look up any agent’s DID to check whether it has a verified human owner.