How to Execute an Approved Proposal

Prerequisites

• The proposal has been anchored on-chain (ckb-firewall anchor) — see How to anchor a proposal
• The PBLK anchor cell has aged at least 72 hours — the review window is enforced at consensus, not by the CLI
• At least threshold-many validator yes-votes are collected locally — see How to vote and How to share proposals
• Run ckb-firewall proposals --status approved to confirm

Execute (treasury-funded, keyless)

For registries with a treasury-lock:

ckb-firewall execute --proposal <id>

No private key required. The treasury-lock funds any registry cell capacity growth. The anchor cell capacity returns to the treasury automatically.

To write the tx to a file without submitting:

ckb-firewall execute --proposal <id> --tx-out gov_tx.json

Execute for all ready proposals

ckb-firewall execute --ready

Finds and executes all proposals that have passed their review window and met the vote threshold.

After execution

The registry cell is updated with the new BLKL v2 payload. Verify:

ckb-firewall inspect
ckb-firewall check --lock-args <the proposed address>

The entry should appear in the registry and check should confirm it is blacklisted (for an add proposal).