Introduction

libID lets an address prove it holds a GitHub, X or Google account. The proof is checked on chain, and the result is stored in the IdentityRegistry contract. Any app or contract can then ask who holds @octocat, or which identities an address holds, by reading the chain. There is no libID server to ask. You still rely on the platforms, the notary and the contract owners; see What a binding proves.

With that you can:

• show a name instead of an address,
• send funds to a handle, even before anyone holds it,
• let only verified accounts call a contract,
• resolve a handle as an ENS name, such as octocat.github.handles.link (not live yet).

Start here

• Quickstart: read your first binding in a few minutes.
• Test on a local chain: run everything on your machine with known test data.

Guides

• Look up a wallet
• Resolve a handle
• Gate a contract
• Send funds to a handle
• Listen to events
• ENS names

Before you build on it

• What a binding proves, and whom you trust for it.
• Security: the contracts have not been audited.
• Networks: what is deployed where.