All lessons · CCC (TypeScript SDK) · Start here · Glossary
Classifying sendTransaction failures before dropping a pending CKB transactionWorkingFrom one fix
From one fix · Check: partly right · Checked 2026-11-19
A failed or timed out ccc client.sendTransaction, or a getTransaction status of "rejected" or "unknown", does not prove the transaction can never commit: a node may have taken it, and "rejected" also covers pool removals such as expiry or a full pool. Store the signed bytes before sending. Drop the pending state only on final refusals (ErrorClientVerification, ErrorClientMaxFeeRateExceeded, TransactionFailedToVerify, PoolRejectedMalformedTransaction), or when an input is not live, the transaction that created that input is committed, and the node no longer holds your transaction as pending, proposed or committed. A not-live input alone is not proof, because CCC's getCellLive also returns not live for a cell the node has not seen. Otherwise resend the stored bytes, treating ErrorClientDuplicatedTransaction and PoolRejectedDuplicatedTransaction as success.
Why it matters: Clearing the pending change on a timeout or a non-final rejection loses track of a transaction that a node may still commit, so the account's settings and address diverge from the chain.
Pattern
if (error instanceof ccc.ErrorClientVerification || error instanceof ccc.ErrorClientMaxFeeRateExceeded) return true;Taken from the commit, shortened.
A test changed in the same commit
It sits next to the fix. We did not run it.
- officialcmg/ckb-keyway:
tests/recovery-postgres.test.ts,tests/user-wallet.test.ts
- Concepts
- Network and RPC reliability, Transaction building and fees
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-08
- Last changed
- 2026-11-08
- 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-08 · officialcmg/ckb-keyway · more from this project
More about CCC (TypeScript SDK)
- CCC client cache can keep dropped transactions; check status without cache
- Clamp the node's get_fee_rate_statistics median before using it as a fee rate
- Persist the transaction hash before broadcasting it
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Classifying sendTransaction failures before dropping a pending CKB transaction", CKB lessons, https://pulse.lusocryptolabs.com/learned/ccc/classifying-sendtransaction-failures-before-dropping-a-pendi, CC BY 4.0, last changed 2026-11-08.