全部经验 · Developer tooling · 从这里开始 · 术语表
Shape of ckb-cli deploy sign-txs output实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
`ckb-cli deploy sign-txs` prints two maps, `cell_tx_signatures` and `dep_group_tx_signatures`, for the deploy info file's `cell_tx` and `dep_group_tx`. Each map goes from lock args (20 bytes, or 28 for multisig args with a since) to one 65 byte signature. It prints YAML-style text by default and a JSON object with `--output-format json`, and the YAML writer prints an empty map inline as `cell_tx_signatures: {}`, so a parser collecting multisig signatures must accept both shapes and the inline empty header.
为什么重要: A parser that expects only one output shape, or only block-style headers, misses sections or signatures. Collected signatures then get attached to the wrong deploy transaction or silently dropped.
代码模式
const HEADER = /^(cell_tx_signatures|dep_group_tx_signatures):\s*(\{\s*\})?$/;摘自提交,已缩短。
- 概念
- Witnesses and signatures, Data encoding (molecule, hex, bigints)
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-08
- 最近改动
- 2026-11-08
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-08 · ILE-Labs/ckb-msig · 这个项目的更多经验
更多关于Developer tooling
- ckb-vm-js 0.2.0 (npm) checks header hash instead of rejecting the field
- Matching a Script code_hash to its code Cell by hash_type
- ckb-cli deploy info file layout for offline multisig signing
引用这条经验
LusoCryptoLabs, "Shape of ckb-cli deploy sign-txs output", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/shape-of-ckb-cli-deploy-sign-txs-output, CC BY 4.0, last changed 2026-11-08.