CKB Pulse

All lessons · Wallets and signing · Start here · Glossary

Keep at least 61 CKB in the change cell when sending from a secp256k1 walletBasicFrom one fix

From one fix · Check: partly right · Checked 2026-11-19

A plain secp256k1_blake160 cell occupies 61 CKB, so when a wallet sends X it must keep at least 61 CKB (the occupied capacity of its own lock) in the change cell, plus the fee, and refuse the send otherwise. The recipient output must also be at least the occupied capacity of the recipient's lock, never less than 61 CKB for a plain address. Enforce the change floor in the transaction builder, and use extra headroom (this runner uses threshold >= amount + 100) for automatic sweeps so fee and change always fit.

Why it matters: A transaction whose change or recipient output holds less than its occupied capacity (61 CKB for a plain secp256k1 cell) is rejected by the node, so the send fails.

A test changed in the same commit

It sits next to the fix. We did not run it.

Concepts
Capacity and cell size, Transaction building and fees
Evidence
From one fix: from one project, checked against its commit
First seen
2026-10-21
Last changed
2026-10-21
Last checked
2026-11-19
Check against the commit
partly right: a true core, with a part that is loose or too wide

Sources (1)

More about Wallets and signing

All 23 in this topic

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

Cite this lesson
LusoCryptoLabs, "Keep at least 61 CKB in the change cell when sending from a secp256k1 wallet", CKB lessons, https://pulse.lusocryptolabs.com/learned/wallets/keep-at-least-61-ckb-in-the-change-cell-when-sending-from-a, CC BY 4.0, last changed 2026-10-21.

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.