全部经验 · Rust scripts and ckb-std · 从这里开始 · 术语表
Keep other WitnessArgs fields when signing sighash_all in tests实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
When a test signer for the secp256k1 sighash_all lock fills the first witness of a script group, it should parse the existing WitnessArgs (for example one with data in output_type) and replace only the lock field: zeroed to 65 bytes while hashing, then set to the signature. Building a fresh WitnessArgs drops output_type or input_type data that a type script reads, and sighash_all hashes the whole first witness with only the lock zeroed, so those fields must already be in place when hashing.
为什么重要: A signer that writes a fresh WitnessArgs silently drops the data a type script reads from output_type or input_type, here the stake owner's consent signature, so the registry script rejects the transaction. If those fields were added after signing instead, the sighash_all signature would no longer match.
代码模式
let zero_lock = existing.clone().as_builder().lock(Some(Bytes::from(vec![0u8; 65])).pack()).build();摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- ckb-service-runner/ckb-service-runner:
acceptance/a8/p1.test.mjs,contracts/csr-contract-tests/tests/job.rs,contracts/csr-contract-tests/tests/registry.rs
- 概念
- Witnesses and signatures, Testing and devnet
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-20
- 最近改动
- 2026-10-20
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-20 · ckb-service-runner/ckb-service-runner · 这个项目的更多经验
更多关于Rust scripts and ckb-std
- ckb-std C shim needs a RISC-V C toolchain (clang) in CI
- Median time vs tip timestamp for deadlines
- Use raw_data(), not as_slice(), when parsing a packed::Bytes witness
引用这条经验
LusoCryptoLabs, "Keep other WitnessArgs fields when signing sighash_all in tests", CKB lessons, https://pulse.lusocryptolabs.com/learned/scripts/keep-other-witnessargs-fields-when-signing-sighash-all-in-te, CC BY 4.0, last changed 2026-10-20.