All lessons · Other · Start here · Glossary
Absolute epoch since needs the 0x20 metric flagWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
An input's since meant as an absolute epoch must have bit 61 set (0x2000000000000000) with bit 63 (relative) and bit 62 clear (RFC 0017). With all three top bits zero the node reads the same number as an absolute block number. The epoch number is in the low 24 bits (raw & 0xffffff), with index and length above it, so check the epoch number inclusively against the required epoch before signing.
Why it matters: Without the 0x20 metric flag the node reads the since value as an absolute block number, so the lock means something entirely different and the contract's epoch check rejects the transaction.
since flag bits, not covered
A test changed in the same commit
It sits next to the fix. We did not run it.
- toastmanAu/daowow:
apps/web/test/lifecycle-rules.test.js
- Concepts
- Since and time locks
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-09-25
- Last changed
- 2026-09-25
- 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-09-25 · toastmanAu/daowow · more from this project
More about Other
- Nervos DAO phase-one withdrawal layout
- Nervos DAO phase-two withdrawal since and amount
- Recognizing a Nervos DAO deposit cell (not a withdrawing one)
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Absolute epoch since needs the 0x20 metric flag", CKB lessons, https://pulse.lusocryptolabs.com/learned/other/absolute-epoch-since-needs-the-0x20-metric-flag, CC BY 4.0, last changed 2026-09-25.