All lessons · Developer tooling · Start here · Glossary
ckb-debugger verifies one script group per runWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
`full` is a VM mode, and by default ckb-debugger runs only input 0's lock, which may be an always-success lock. To check a whole transaction, enumerate every input lock, input type and output type group, run each with --script-group-type/--cell-type/--cell-index, and sum the cycles. Pair each accepted case with a control that must fail with an exact error code.
Why it matters: Running ckb-debugger on a mock tx without selecting script groups only executes input 0's lock, so a test can pass on an always-success lock (634 cycles) while the contract scripts never run, and the cycle budget is mismeasured.
Pattern
spawn ckb-debugger --tx-file mock.json (no group selection) and treat exit 0 as the whole tx passingA test changed in the same commit
It sits next to the fix. We did not run it.
- toastmanAu/daowow:
apps/web/test/claim-debugger.test.js
- Concepts
- Testing and devnet, Transaction building and fees
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-14
- Last changed
- 2026-11-14
- Last checked
- 2026-11-19
- Check against the commit
- right: the lesson follows from its commit and still holds in the code today
Sources (1)
- 2026-11-14 · toastmanAu/daowow · more from this project
More about 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
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "ckb-debugger verifies one script group per run", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/ckb-debugger-verifies-one-script-group-per-run, CC BY 4.0, last changed 2026-11-14.