CKB Pulse

全部经验 · Other · 从这里开始 · 术语表

Range check since epoch fields instead of masking them实践来自一次修复

来自一次修复 · 核对结果:正确 · 核对于 2026-11-21

When packing an epoch-based since value (24-bit epoch number, 16-bit index, 16-bit length), masking an out-of-range epoch silently wraps it into a much earlier deadline. This commit's packSince now throws a RangeError for any field outside its bit width, and createTranfr/renewTranfr check that tip epoch plus duration fits within 0xFFFFFF before packing.

为什么重要: Masking an epoch number above 0xFFFFFF silently wraps it into a much earlier since deadline, so the time lock can open far sooner than the caller intended with no error raised.

The existing since lesson covers the metric flag bits. This card is about range checking the epoch number, index and length fields rather than masking them.

代码模式

避免
((epoch & NUMBER_MASK) << NUMBER_OFFSET)

摘自提交,已缩短。

同一提交中改动了测试

它与修复在一起,我们没有运行它。

概念
Since and time locks, Data encoding (molecule, hex, bigints)
证据
来自一次修复: 来自一个项目,已对照其提交核对
首次出现
2026-11-20
最近改动
2026-11-20
最近核对
2026-11-21
对照提交的核对结果
正确:这条经验出自该提交,并且在今天的代码中仍然成立

来源(1)

更多关于Other

查看此主题的全部 10 条

你维护这条经验的来源项目吗?请确认或纠正

引用这条经验
LusoCryptoLabs, "Range check since epoch fields instead of masking them", CKB lessons, https://pulse.lusocryptolabs.com/learned/other/range-check-since-epoch-fields-instead-of-masking-them, CC BY 4.0, last changed 2026-11-20.

取自公开提交,并对照每条经验的来源提交和项目当前代码做了核对。使用前请先读来源。 文本采用 CC BY 4.0:请署名 LusoCryptoLabs, CKB lessons,并附上经验的链接。 想修改或撤下某条经验?请提交 issue。