CKB Pulse

All lessons · Developer tooling · Start here · Glossary

Shape of ckb-cli deploy sign-txs outputWorkingFrom one fix

From one fix · Check: right · Checked 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.

Why it matters: 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.

Pattern

Prefer
const HEADER = /^(cell_tx_signatures|dep_group_tx_signatures):\s*(\{\s*\})?$/;

Taken from the commit, shortened.

Concepts
Witnesses and signatures, Data encoding (molecule, hex, bigints)
Evidence
From one fix: from one project, checked against its commit
First seen
2026-11-08
Last changed
2026-11-08
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)

More about Developer tooling

All 35 in this topic

Do you maintain a project this lesson came from? Confirm or correct it

Cite this lesson
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.

Drawn from public commits and checked against the commit each one came from and the project's code today. Read the source before you rely on one. Text under CC BY 4.0: credit LusoCryptoLabs, CKB lessons, with a link to the lesson. Want a lesson changed or removed? Open an issue.