All lessons · CCC (TypeScript SDK) · Start here · Glossary
CCC client cache can keep dropped transactions; check status without cacheWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
A ccc client records the transactions it sends in its cache, so a claim or sweep the chain dropped or rejected stays there with its outputs usable and its inputs spent, which breaks later sends. Check such transactions with client.getTransactionNoCache and treat an undefined result or status "rejected" as dropped. Rebuild that client's cache from the chain before building new sends, and give automated sends their own ccc client so this rebuild does not touch the account's other pending transactions.
Why it matters: A dropped claim or sweep left in ccc's cache keeps its payout looking usable and its fee reserve looking spent, so every later claim built from that cache fails.
Related to the cache clearing and getTransactionNoCache lessons, but adds a distinct remedy: treat undefined or rejected as dropped, and use a separate client for automated sends to isolate its cache.
Pattern
const found = await nodeKeyClient.getTransactionNoCache(txHash).catch(() => null);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/api-client.test.ts,tests/browser-watchtower.test.ts,tests/channel-openings.test.ts,tests/logout-handoff.test.ts,tests/node-backup-postgres.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-17
- Last changed
- 2026-11-17
- 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-11-17 · officialcmg/ckb-keyway · more from this project
More about CCC (TypeScript SDK)
- Clamp the node's get_fee_rate_statistics median before using it as a fee rate
- Classifying sendTransaction failures before dropping a pending CKB transaction
- Persist the transaction hash before broadcasting it
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "CCC client cache can keep dropped transactions; check status without cache", CKB lessons, https://pulse.lusocryptolabs.com/learned/ccc/ccc-client-cache-can-keep-dropped-transactions-check-status, CC BY 4.0, last changed 2026-11-17.