All lessons · Developer tooling · Start here · Glossary
ckb-cli deploy gen-txs does not check the block size limitWorkingFrom one fix
From one fix · Check: right · Checked 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.
Why it matters: 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.
Pattern
const BLOCK_SIZE_LIMIT = 597000; const estimate = total + OVERHEAD_BASE + OVERHEAD_PER_CELL * files.length;Taken from the commit, shortened.
- Concepts
- Transaction building and fees, Capacity and cell size
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-09-18
- Last changed
- 2026-09-18
- 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)
- 2026-09-18 · toastmanAu/daowow · more from this project
More about 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
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
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.