全部经验 · Rust scripts and ckb-std · 从这里开始 · 术语表
Relative block number since uses top byte 0x80, not the absolute epoch 0x20实践来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 2026-11-19
Under RFC 0017 since encoding, bit 63 marks relative and bits 61 to 62 select the metric (00 is block number), so a relative block count is RELATIVE_BLOCK_FLAG (0x8000000000000000) OR the count, and 256 blocks becomes 0x8000000000000100. In this commit the type script checks since >> 56 == 0x80, so reusing the absolute epoch form (top byte 0x20) is rejected on chain with an error code that does not name the since as the cause.
为什么重要: If the absolute epoch flag 0x20 is reused where the script expects a relative block number, the transaction is refused on chain with a generic script error that does not point at the since.
代码模式
return RELATIVE_BLOCK_FLAG | n;摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/daowow:
apps/web/test/entropy-tx.test.js - toastmanAu/daowow:
apps/web/test/lifecycle-rules.test.js
- 概念
- Since and time locks
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-02
- 最近改动
- 2026-10-02
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(2)
- 2026-10-02 · toastmanAu/daowow · 这个项目的更多经验
- 2026-10-02 · toastmanAu/daowow · 这个项目的更多经验
更多关于Rust scripts and ckb-std
引用这条经验
LusoCryptoLabs, "Relative block number since uses top byte 0x80, not the absolute epoch 0x20", CKB lessons, https://pulse.lusocryptolabs.com/learned/scripts/relative-block-number-since-uses-top-byte-0x80-not-the-absol, CC BY 4.0, last changed 2026-10-02.