全部经验 · Developer tooling · 从这里开始 · 术语表
ckb-cli deploy gen-txs does not check the block size limit实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
`ckb-cli deploy gen-txs` checks capacity and reports success even when the deployment transaction exceeds the 597,000 byte block size limit; the node only rejects it at broadcast with ExceededMaximumBlockBytes. When deploying several large contract binaries, sum their sizes before signing and split them across separate deployment configs (sending each transaction only after the previous one confirms) if they approach the limit.
为什么重要: The deployer signs a transaction that gen-txs reported as successful, and only learns at broadcast that the node refuses it with ExceededMaximumBlockBytes because the combined binaries push it past the 597,000 byte block size limit.
代码模式
const BLOCK_SIZE_LIMIT = 597000; const estimate = total + OVERHEAD_BASE + OVERHEAD_PER_CELL * files.length;摘自提交,已缩短。
- 概念
- Transaction building and fees, Capacity and cell size
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-09-18
- 最近改动
- 2026-09-18
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-09-18 · 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 init overwrites an existing tx file with an empty skeleton
引用这条经验
LusoCryptoLabs, "ckb-cli deploy gen-txs does not check the block size limit", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/ckb-cli-deploy-gen-txs-does-not-check-the-block-size-limit, CC BY 4.0, last changed 2026-09-18.