全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Confirm a committed transaction is on the canonical chain via get_header and get_block_hash实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
Before recording a transaction as committed, you can cross-check get_transaction's tx_status.block_hash. Call get_header on that hash and require get_block_hash(header.number) to return the same hash. If the header is missing or the hashes differ, keep the transaction marked uncertain and reconcile it later rather than building new transactions on its outputs.
为什么重要: Without the cross-check, the app may record a transaction as settled and build later state on its outputs even if the block was reorged out between RPC reads.
代码模式
推荐
const header=await rpc('get_header',[tx.tx_status.block_hash]);return !!header && await rpc('get_block_hash',[header.number])===header.hash;摘自提交,已缩短。
- 概念
- Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-05
- 最近改动
- 2026-11-05
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-05 · Ticoworld/QuotaCell · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- 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
- send_transaction error -1111 (PoolRejectedRBF) is a conflict, not "already in pool"
引用这条经验
LusoCryptoLabs, "Confirm a committed transaction is on the canonical chain via get_header and get_block_hash", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/confirm-a-committed-transaction-is-on-the-canonical-chain-vi, CC BY 4.0, last changed 2026-11-05.