全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
A rejected or unknown get_transaction status does not make a signed transaction dead实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
A node reporting a transaction you sent as rejected or unknown does not prove it is dead: one node's answer is not proof, and while all its inputs are live the signed bytes could still be rebroadcast by someone and commit. Only release its reserved inputs if a later transaction is guaranteed to conflict with it (here a shared pool cell every later action must spend, so at most one can commit), and also require that every input is still live, that the status is still rejected or unknown when rechecked after the input reads, and that the submission is old enough (2 minutes here), behind an explicit confirmation.
为什么重要: If inputs are freed on a single node's rejected or unknown report, a new action can be built that does not conflict with the old signed transaction, and both may commit if someone rebroadcasts the old bytes while its inputs are still live.
代码模式
requireRecovery(poolInput,'not a pool transaction; nothing guarantees a later conflict');同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/openswap:
frontend/test/pools.spec.ts,pool-sdk/test/recovery.test.ts
- 概念
- Transaction building and fees, Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-26
- 最近改动
- 2026-10-26
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-26 · toastmanAu/openswap · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- send_transaction error -1111 (PoolRejectedRBF) is a conflict, not "already in pool"
- Check indexer lag with get_indexer_tip before signing
- Check original tx unknown and input live on independent nodes before same input cancellation
引用这条经验
LusoCryptoLabs, "A rejected or unknown get_transaction status does not make a signed transaction dead", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/a-rejected-or-unknown-get-transaction-status-does-not-make-a, CC BY 4.0, last changed 2026-10-26.