All lessons · CKB node, RPC and indexer · Start here · Glossary
Serialize transfers from one account until the previous tx is committedWorkingFrom one fix
From one fix · Check: right · Checked 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.
Why it matters: 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.
Pattern
this.queue = run.then((c) => this.committed(c.hash), () => undefined);Taken from the commit, shortened.
- Concepts
- Transaction building and fees, Network and RPC reliability
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-10-30
- Last changed
- 2026-10-30
- 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-10-30 · wildanrhmn/ckb-devnet-explorer · more from this project
More about 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
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
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.