All lessons · CKB node, RPC and indexer · Start here · Glossary
Reconcile a lost send_transaction response by pinned hash, not by rebuildingWorkingFrom one fix
From one fix · Check: partly right · Checked 2026-11-19
When a send_transaction response is lost (the node may already have accepted the transaction), this commit pins the signed transaction hash and its input outpoints, and recovers by querying get_transaction for that exact hash and get_live_cell for each input instead of building a new payment. Only a 'committed' status ends the intent; rejected, unknown or spent inputs stay 'uncertain' for operator review, because a fresh rebuild from refreshed cells was shown to let a second payment to the same recipient commit.
Why it matters: Building a new payment after a lost response can create a second, different transaction that also commits, paying the same invoice twice.
Pattern
state = "committed" if chain_state == "committed" else "uncertain"Taken from the commit, shortened.
- Concepts
- Network and RPC reliability, Transaction building and fees, Indexer queries and cell collection
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-02
- Last changed
- 2026-11-02
- Last checked
- 2026-11-19
- Check against the commit
- partly right: a true core, with a part that is loose or too wide
Sources (1)
- 2026-11-02 · Ticoworld/QuotaCell · more from this project
More about CKB node, RPC and indexer
- Check indexer lag with get_indexer_tip before signing
- get_live_cell may return "unknown" rather than "dead" for a spent output
- 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, "Reconcile a lost send_transaction response by pinned hash, not by rebuilding", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/reconcile-a-lost-send-transaction-response-by-pinned-hash-no, CC BY 4.0, last changed 2026-11-02.