All lessons · CKB node, RPC and indexer · Start here · Glossary
Confirm a committed transaction is on the canonical chain via get_header and get_block_hashWorkingFrom one fix
From one fix · Check: right · Checked 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.
Why it matters: 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.
Pattern
const header=await rpc('get_header',[tx.tx_status.block_hash]);return !!header && await rpc('get_block_hash',[header.number])===header.hash;Taken from the commit, shortened.
- Concepts
- Network and RPC reliability
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-05
- Last changed
- 2026-11-05
- 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-05 · Ticoworld/QuotaCell · more from this project
More about 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"
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
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.