All lessons · Apps and UI · Start here · Glossary
Lock-based fallback when a stored out point goes staleWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
A saved out point stops being valid once the cell is consumed and recreated. Use the recorded out point if it is still live; otherwise find the unique live cell matching the exact lock (code_hash, hash_type, args). In both cases, still check the cell's contents against the recorded values.
Why it matters: After the cell is consumed and recreated (here by Arm), a lookup that filters only by the recorded out point finds nothing, so verification of a valid switch fails.
Pattern
filtering live cells only by the recorded out_point → no match after the cell was replaced; prefer recorded match if present else unique cell matching lock scriptA test changed in the same commit
It sits next to the fix. We did not run it.
- psawyerberlin/ckb-revocable-timelock:
client/test/chain.test.ts
- Concepts
- Indexer queries and cell collection
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-15
- Last changed
- 2026-11-15
- 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-15 · psawyerberlin/ckb-revocable-timelock · more from this project
More about Apps and UI
- Resolving cell deps per cell after redeploying a data-hashed script
- Exact CKB-to-shannon conversion with BigInt
- Nervos DAO hold time with term-locked withdrawals
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Lock-based fallback when a stored out point goes stale", CKB lessons, https://pulse.lusocryptolabs.com/learned/apps/lock-based-fallback-when-a-stored-out-point-goes-stale, CC BY 4.0, last changed 2026-11-15.