CRT CKB Revocable Timelock

Run a CRT node

If you already run CSR beside your CKB node, CRT is one more service to switch on. Your node does not change. You hold one small secret per switch that chose you, you are paid a tip every day you keep it, and the chain decides when you publish it.

What you commit to

What you cannot do, by construction: release early — consensus refuses the transaction until the deadline — or release something false — the lock verifies the key against the public key you committed. What you could do and must not: copy a key out of your storage. Users are told this is outside what CRT can prevent, which is why switches spread across several runners and thresholds.

What you earn

Default tipsCKB
Key generation, once per switch1
Heartbeat, once a day per switch0.5
Per switch and year≈ 183

Tips go to your runner wallet like every CSR tip and are swept to your address by CSR. At $0.01 per CKB a switch brings you about $1.80 a year.

A launch-phase runner is a contribution to the network, not income. The first realistic use is your own switch: run a node, mark it mandatory, and no coalition of strangers can open your switch without you.

Enable in one command

Needs a CSR release with the random_bytes host call (check csr version against the release notes).

curl -fLO https://raw.githubusercontent.com/psawyerberlin/ckb-revocable-timelock/main/scripts/crt-enable.sh
sudo -u csr bash crt-enable.sh --network testnet
  1. Reads your runner lock hash from the running CSR instance.
  2. Downloads the released service binary and checks its SHA-256 against the release’s signed checksum list.
  3. Writes a local manifest with your lock hash as the service argument. This is what addresses CRT jobs to you rather than to any runner: the service ID clients compute includes it.
  4. Adds, approves and enables the service in CSR, and prints your CRT service ID and the dashboard link.

Nothing has to be published. Clients derive your service ID from public data. To appear in the app’s runner directory with a label, open a pull request on deployments/testnet-runners.json — optional.

Watch it run

The CSR dashboard’s Jobs page shows every CRT run with a short result: hold, keygen, release, done, cancelled, dropped — and key lost, which means your storage lost a key and needs your attention. service_data/deletions.log lists the keys CSR deleted on cancellation, never their content.

Leaving

scripts/crt-disable.sh disables and revokes the service. Switches that chose you lose a node; their owners see their margin shrink and can rewrap. Keys already stored remain until their Alive Cells die unless you delete them by hand. Announce before you leave, and give people time to rewrap.

Full operator guide: docs/operators.md.