Skip to main content
Everything on this page happens on the Billions testnet, so you can try it freely. Records you create here are separate from the production registry.

​
Read-only use needs nothing

Searching, browsing agents, opening attestations and viewing schemas all work without signing in. You only need the setup below to write: create a schema, make an attestation, or revoke one.

​
Before you write

You need two things.
  1. An EVM wallet with testnet gas. Writes are transactions on the Billions testnet (chain ID 6913), and your wallet pays the gas.
  2. A Billions identity linked to that wallet. The registry records who made each attestation as an iden3 identity, not just an address. The link between your wallet address and your identity is stored on-chain in the Identity Verifier contract.

​
Connect your wallet

1

Connect

Click the connect button in the top right and choose your wallet. The Explorer connects through WalletConnect, so most EVM wallets work. Your shortened address replaces the button.
2

Open your account menu

Click your address. The menu shows a DID badge. If your wallet isn’t linked yet it reads No DID, with a Connect link beside it.
3

Link your Billions identity

Click Connect. You’re sent to the Billions web wallet with a linking request. Approve it there and you’re redirected back.
4

Confirm

The Explorer checks the Identity Verifier contract every ten seconds. Once the link is recorded on-chain, your DID appears in the menu and write actions unlock.
The linking request is sent to the Billions web wallet, which needs an identity to link. If you don’t have one yet, create it in the Billions Wallet first.

​
Look something up

Use the search box, or paste into it directly:
  • An agent DID shows the human it’s attested to.
  • A human DID shows all the agents attested to it.
  • A schema ID or name opens that schema.
  • An attestation ID opens the attestation.
From any attestation row you can copy the attester’s and recipient’s DID, ID and address. You’ll need those for the next section.

​
Create a schema

1

Open the form

Go to Schemas and click Create schema.
2

Name it and add fields

Enter a schema name, then add fields. Each has a name and a type: string, uint256, address, bytes, bool and so on. Tick Array to make a field a list of that type.
3

Resolver (optional)

Enter a resolver contract address only if you’ve deployed one that should vet attestations. Leave it empty otherwise.
4

Revocable

Tick the box if attestations of this schema should ever be revocable. Decide now: it is part of the schema’s registration.
5

Submit

Click Create schema and confirm the transaction in your wallet. When it’s mined you get a schema ID, which you can search for and use to make attestations.
For what each option means, see Schemas.

​
Make an attestation

This example leaves a review for an agent. The Review schema has no resolver, so any linked wallet can use it.
1

Pick the schema

Open Attestations, click to make an attestation, and search for the schema by name, ID or number. Select Review.
2

Fill in the data

The form shows one input per schema field. For Review, enter stars as a number from 0 to 255 (the field is a uint8) and comment as text. The form validates each value against its type before it lets you submit.
3

Check the issuer

The Issuer block shows the chain ID, registry address and your issuer ID. These are filled in from your connected identity and can’t be edited.
4

Enter the recipient

Fill in all three recipient fields for the agent you’re reviewing:
5

Choose revocability

Tick Allow this attestation to be revoked later if you want the option. If the schema is non-revocable the box is disabled, with a tooltip saying so.
6

Submit

Click Make attestation and confirm in your wallet. After the transaction is mined you’re taken to the attestations list, where yours appears once the indexer picks it up.
If Make attestation stays disabled, a field is empty or fails validation, or the schema is one the Explorer can’t decode into fields. Schemas it can’t decode are shown as “Non-standard schema” and can’t be attested through the form. Those need to be attested to from code, as in the example repo below.

​
Revoke an attestation

Open the attestation’s detail page and click Revoke, then confirm the transaction. When the attestation was created as non-revocable, the button is inactive and its tooltip reads “Attestations created with this schema cannot be revoked.” A revoked attestation stays visible with its revocation time. Anything that checks validity, including the revoked field in the API, will show it as revoked.

​
Confirm it worked

Look your attestation up three ways to see that they agree:
  1. In the Explorer, search for the attestation ID.
  2. In the API, GET /attestations/<id>.
  3. In the block explorer, open the transaction hash from the attestation detail page.

​
Try the example scripts

To test the same operations from code, clone BillionsNetwork/attestations-examples and follow its README. It has ready-made scripts for leaving and reading reviews, creating a custom schema and attestation, checking ownership, and revoking, all pointed at the testnet. Use a throwaway wallet funded with testnet gas, since you put its private key in a local .env file.

​
Next

Testnet API

Query what you just created over HTTP.