Testnet Deployment

Use this page if you want the canonical testnet values the SDKs and CLI are built around.

Two different outpoints

The contract binary outpoints are for deployment metadata. The canonical registry cell outpoint is the one your SDK and CLI use as live data.

What is published

• The registry type script identity
• The canonical registry cell outpoint and data
• The deployed contract binary outpoints
• Deployment history for traceability

How to use it

1. Read notes/deployments/testnet.registry.json for the current canonical values.
2. Use the registryScript in the TypeScript SDK.
3. Fetch the live canonicalRegistryCell data and pass it as the registry cell dep.
4. Use the CLI for inspection or governance transaction preparation.

For the exact chain call, use:

ckb-cli --url https://testnet.ckb.dev rpc get_live_cell \
  --tx-hash 0x57edc162ddd476d970b8a65558466ca11bb1762be9366fd12c76d620fe695fb7 \
  --index 0 \
  --with-data \
  --output-format json

SDK

Use registryScript plus canonicalRegistryCell.data.

CLI

Use ckb-firewall inspect or the governance commands against the live registry outpoint.

Important distinction

The deployment outpoints for the contract binaries are not the same thing as the live registry payload.

• Contract binary cells contain the RISC-V program
• Registry cell data contains the BLKL payload

That is the bit developers usually miss on the first read.

That distinction matters when you wire up the SDK or inspect chain state.