全部经验 · Developer tooling · 从这里开始 · 术语表
Charging load_program bytes as cycles when building a custom ckb-vm machine进阶来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
When you build a ckb-vm machine yourself (DefaultMachineBuilder or AsmMachine) and call load_program, charge the returned byte count with machine.add_cycles_no_checking(ckb_script::cost_model::transferred_byte_cycles(bytes)). That count covers the loaded program and the stack and argument setup, and TransactionScriptsVerifier charges it on chain, so without it your cycle count comes out too low (in ckb-debugger the fib test went from 1361 to 3364 cycles). For AsmMachine call it on the inner machine, and pass the error up instead of unwrapping.
为什么重要: A hand-built ckb-vm machine that skips charging the loaded program bytes reports fewer cycles than on-chain verification does (the fib example showed 1361 instead of 3364), so cycle estimates and limits based on it are wrong.
代码模式
machine.add_cycles_no_checking(transferred_byte_cycles(bytes))?;摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- nervosnetwork/ckb-standalone-debugger:
ckb-debugger/tests/test_command.rs
- 概念
- Testing and devnet, Other
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-03
- 最近改动
- 2026-11-03
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-03 · nervosnetwork/ckb-standalone-debugger · 这个项目的更多经验
更多关于Developer tooling
- ckb-vm-js 0.2.0 (npm) checks header hash instead of rejecting the field
- Derive devnet Spore and system script cell deps from a fresh OffCKB export
- Pass wasm bytes to ckb-vm-js createVerifier in Node
引用这条经验
LusoCryptoLabs, "Charging load_program bytes as cycles when building a custom ckb-vm machine", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/charging-load-program-bytes-as-cycles-when-building-a-custom, CC BY 4.0, last changed 2026-11-03.