Registry

Discover verified CKB artifacts, deployment records and CellScript packages, or publish with scoped wallet authorisation.

Choose a publisher signing route.

Use a detected CKB connector, or import a signature produced outside this page. A manual wallet link is not a browser connection; the Registry accepts it only after server-side identity and signature verification.

CKB testnet No signing route selected
  1. 01Choose signer
  2. 02Review scope
  3. 03Authorise
Use the CLI authorisation path instead
cellc auth capability create --principal-type <principal_type> --principal-id <principal_id> --scope publish:<namespace>/<name> --expires 90d --json > capability-payload.json cellc auth capability submit --payload capability-payload.json --wallet-signature wallet-signature.json cellc auth namespace claim --namespace <namespace> --payload capability-payload.json --wallet-signature wallet-signature.json

CKB wallet

Choose a wallet

Choose a signing route for this Registry environment. Detected CKB connectors work in-browser; directory entries only open the wallet site and require a compatible wallet-signature.json produced elsewhere.

12 wallets

Direct connectors expose only the public identity and scoped signature. Manual routes require you to paste those public values explicitly; never paste a recovery phrase.