All lessons · CKB node, RPC and indexer · Start here · Glossary
Verify a deployed code cell is canonical and live before recording it as a cell depWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
Before writing a deployment manifest for a code cell, this commit checks get_transaction is committed, that get_block_hash at the header number equals the block hash (not reorganized), and that get_live_cell still reports status live with the expected data hash. It then repeats the canonical and live checks after all reads (on two independent RPCs), so a stale, spent or reorganized cell never yields a manifest.
Why it matters: Without these checks a manifest can pin a cell dep out point whose deployment was reorganized away, whose cell was spent, or whose data is not the expected code, so every later transaction that references it fails verification.
Pattern
assert.equal(await source('get_block_hash',[primary.blockNumber]),primary.blockHash,'Deployment reorganized');Taken from the commit, shortened.
- Concepts
- Cell deps and script lookup, Network and RPC reliability
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-09
- Last changed
- 2026-11-09
- Last checked
- 2026-11-19
- Check against the commit
- right: the lesson follows from its commit and still holds in the code today
Sources (1)
- 2026-11-09 · Ticoworld/QuotaCell · more from this project
More about CKB node, RPC and indexer
- Check chain-wide script users before consuming a deployed code cell
- get_live_cell may return "unknown" rather than "dead" for a spent output
- get_transaction returns an object with a null transaction for rejected and unknown txs
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Verify a deployed code cell is canonical and live before recording it as a cell dep", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/verify-a-deployed-code-cell-is-canonical-and-live-before-rec, CC BY 4.0, last changed 2026-11-09.