Skip to content
CKB Transaction Firewall CKB Transaction Firewall

Step 3: Verify the Deployment

Once the bootstrap transaction is confirmed, verify that both the registry cell and the treasury pool are live and correctly configured.

Inspect the registry

Section titled “Inspect the registry”
Terminal window
ckb-firewall inspect \
  --rpc-url https://testnet.ckb.dev \
  --registry-tx <bootstrap tx hash from step 2> \
  --registry-index 0

Expected output:

Registry: <bootstrap tx hash>:0
Entries:  0 (empty)
Validators: 5 | Threshold: 3-of-5
Treasury pool: 100,000.0 CKB (available)

The treasury pool balance shows as available immediately — the bootstrap seeded 100,000 CKB at output index 1. No separate seeding step is required.

Record the type_id_value

Section titled “Record the type_id_value”

The type_id_value is printed in the inspect output under “Registry identity”. It is also in deploy/bootstrap-tx.json under registryCell.typeIdValue.

This 32-byte hex value is the stable identity of your registry. It never changes across governance updates and must be embedded in every firewall lock args configuration that consults this registry.

Check treasury health

Section titled “Check treasury health”
Terminal window
ckb-firewall inspect \
  --rpc-url https://testnet.ckb.dev \
  --registry-tx <bootstrap tx hash> \
  --registry-index 0 \
  --show-treasury

When pool usage reaches 70%, inspect and the GUI warn and display the donation address. The 100,000 CKB seed covers roughly 330 proposal anchor operations before reaching that threshold.

Top up if needed

Section titled “Top up if needed”

To donate more CKB to the treasury pool:

Terminal window
ckb-cli --url https://testnet.ckb.dev wallet transfer \
  --to-address <treasury address shown in inspect> \
  --capacity <amount> \
  --fee-rate 1000

Continue to Step 4.

Background reading

Section titled “Background reading”