全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Verify a deployed code cell is canonical and live before recording it as a cell dep实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 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.
为什么重要: 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.
代码模式
assert.equal(await source('get_block_hash',[primary.blockNumber]),primary.blockHash,'Deployment reorganized');摘自提交,已缩短。
- 概念
- Cell deps and script lookup, Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-09
- 最近改动
- 2026-11-09
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-09 · Ticoworld/QuotaCell · 这个项目的更多经验
更多关于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
引用这条经验
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.