CKB Pulse

全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表

Decoding the packed epoch field (number, index, length)实践再次出现

再次出现 · 核对结果:正确 · 核对于 2026-11-19

A CKB header epoch field packs the epoch number in the low 24 bits, the index in the next 16 bits (shift 24) and the epoch length in the next 16 bits (shift 40). When estimating time to a target epoch from the tip, subtract the fraction already spent (index * epoch duration / length) and guard against length 0 to avoid division by zero.

为什么重要: Reading the raw epoch hex as a number, or masking it wrongly, gives nonsense epoch numbers for window checks. Ignoring the index fraction makes time-to-epoch estimates off by up to a whole epoch, about four hours.

代码模式

推荐
number: v & 0xffffffn, index: (v >> 24n) & 0xffffn, length: (v >> 40n) & 0xffffn,

摘自提交,已缩短。

同一提交中改动了测试

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

概念
Since and time locks, Data encoding (molecule, hex, bigints)
证据
再次出现: 在两个或以上项目中出现
首次出现
2026-11-10
最近改动
2026-11-10
最近核对
2026-11-19
对照提交的核对结果
正确:这条经验出自该提交,并且在今天的代码中仍然成立

来源(3)

更多关于CKB node, RPC and indexer

查看此主题的全部 45 条

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

引用这条经验
LusoCryptoLabs, "Decoding the packed epoch field (number, index, length)", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/decoding-the-packed-epoch-field-number-index-length, CC BY 4.0, last changed 2026-11-10.

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