全部经验 · Developer tooling · 从这里开始 · 术语表
ckb-cli tx init overwrites an existing tx file with an empty skeleton实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
`ckb-cli tx init --tx-file` creates a new empty transaction file and exits 0, so running it on a prepared transaction silently destroys that transaction. For a prebuilt transaction, write ckb-cli's tx-file wrapper ({transaction, multisig_configs, signatures}) yourself and go straight to `tx info` and `tx sign-inputs`.
为什么重要: Running `tx init` on a prepared transaction file replaces it with an empty skeleton and still reports success, so the transaction is lost and the later steps produce no result.
代码模式
推荐
fs.writeFileSync(outFile, JSON.stringify({ transaction: tx, multisig_configs: {}, signatures: {} }, null, 2));摘自提交,已缩短。
- 概念
- Transaction building and fees, Witnesses and signatures
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-09-23
- 最近改动
- 2026-09-23
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-09-23 · toastmanAu/daowow · 这个项目的更多经验
更多关于Developer tooling
- ckb-cli deploy info file layout for offline multisig signing
- ckb-cli needs --skip-check to sign and send transactions with custom locks
- ckb-cli tx sign-inputs stores signatures in the file's signatures map, not witness 0
引用这条经验
LusoCryptoLabs, "ckb-cli tx init overwrites an existing tx file with an empty skeleton", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/ckb-cli-tx-init-overwrites-an-existing-tx-file-with-an-empty, CC BY 4.0, last changed 2026-09-23.