All lessons · Rust scripts and ckb-std · Start here · Glossary
Creation witness for an output type script goes in WitnessArgs.output_typeWorkingFrom one fix
From one fix · Check: partly right · Checked 2026-11-19
A type script that checks a newly created output can read its proof from WitnessArgs.output_type, but the script decides which witness to read: tactus-o1's state proof script loads absolute witness 0 (Source::Input, index 0), not a witness matched to the output index. If that witness is also the first witness of the secp lock group, put the proof in its output_type field next to the 65 byte lock placeholder, and it is covered by the lock signature because the sighash keeps the other WitnessArgs fields and zeroes only the lock.
Why it matters: If the proof is added after signing, or put in a separate witness the lock does not hash, the signature either fails to verify or does not commit to the proof the type script checks.
- Concepts
- Witnesses and signatures
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-10-10
- Last changed
- 2026-10-10
- Last checked
- 2026-11-19
- Check against the commit
- partly right: a true core, with a part that is loose or too wide
Sources (1)
- 2026-10-10 · Tactus-Labs/tactus-o1 · more from this project
More about Rust scripts and ckb-std
- Use raw_data(), not as_slice(), when parsing a packed::Bytes witness
- CKB blake160 is the first 20 bytes of the 32 byte ckbhash
- Keep other WitnessArgs fields when signing sighash_all in tests
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Creation witness for an output type script goes in WitnessArgs.output_type", CKB lessons, https://pulse.lusocryptolabs.com/learned/scripts/creation-witness-for-an-output-type-script-goes-in-witnessar, CC BY 4.0, last changed 2026-10-10.