全部经验 · Developer tooling · 从这里开始 · 术语表
Verify header_deps against independently fetched headers, not against the tx's own list实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
When checking a transaction that uses header_deps for entropy (for example, headers at fixed offsets from a cell's inclusion block), derive the expected headers yourself: get the creating tx with get_transaction, then get_header on its block_hash, then get_header_by_number for the scheduled heights. Only then compare them to the tx's header_deps. Taking the headers from header_deps makes the check circular, since it only confirms the transaction agrees with itself.
为什么重要: A checker that takes headers from the transaction's own header_deps would approve a transaction listing the wrong blocks, so wrong entropy inputs would reach the node marked safe to send.
代码模式
const h = await rpc.call("get_header_by_number", ["0x" + n.toString(16)]);摘自提交,已缩短。
- 概念
- Since and time locks, Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-02
- 最近改动
- 2026-10-02
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-02 · toastmanAu/daowow · 这个项目的更多经验
更多关于Developer tooling
- Mirror on-chain rules off-chain with mutation tests
- Reset devnets instead of skewing the chain clock
- Separate submit and commit verification environments
引用这条经验
LusoCryptoLabs, "Verify header_deps against independently fetched headers, not against the tx's own list", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/verify-header-deps-against-independently-fetched-headers-not, CC BY 4.0, last changed 2026-10-02.