全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Reconcile a lost send_transaction response by pinned hash, not by rebuilding实践来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 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.
为什么重要: Building a new payment after a lost response can create a second, different transaction that also commits, paying the same invoice twice.
代码模式
state = "committed" if chain_state == "committed" else "uncertain"摘自提交,已缩短。
- 概念
- Network and RPC reliability, Transaction building and fees, Indexer queries and cell collection
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-02
- 最近改动
- 2026-11-02
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(1)
- 2026-11-02 · Ticoworld/QuotaCell · 这个项目的更多经验
更多关于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"
引用这条经验
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.