全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Serialize transfers from one account until the previous tx is committed实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
When one account sends several transfers in a row (here via `offckb transfer`), a new transfer started before the previous one is committed can pick the same input cell, and the node rejects it with PoolRejectedRBF. This faucet queues claims and polls get_transaction until tx_status is committed, rejected or unknown before building the next transfer.
为什么重要: If a second transfer from the same account is built while the first is still in the pool, it selects the same live input cell and the node rejects it with PoolRejectedRBF, so the claim fails.
代码模式
this.queue = run.then((c) => this.committed(c.hash), () => undefined);摘自提交,已缩短。
- 概念
- Transaction building and fees, Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-30
- 最近改动
- 2026-10-30
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-30 · wildanrhmn/ckb-devnet-explorer · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- send_transaction error -1111 (PoolRejectedRBF) is a conflict, not "already in pool"
- A rejected or unknown get_transaction status does not make a signed transaction dead
- Check indexer lag with get_indexer_tip before signing
引用这条经验
LusoCryptoLabs, "Serialize transfers from one account until the previous tx is committed", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/serialize-transfers-from-one-account-until-the-previous-tx-i, CC BY 4.0, last changed 2026-10-30.