全部经验 · Wallets and signing · 从这里开始 · 术语表
Keep at least 61 CKB in the change cell when sending from a secp256k1 wallet基础来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 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.
为什么重要: 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.
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- ckb-service-runner/ckb-service-runner:
acceptance/a8/p2.test.mjs,acceptance/a8/p3.test.mjs,acceptance/a8/p4.test.mjs
- 概念
- Capacity and cell size, Transaction building and fees
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-21
- 最近改动
- 2026-10-21
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(1)
- 2026-10-21 · ckb-service-runner/ckb-service-runner · 这个项目的更多经验
更多关于Wallets and signing
- Placeholder JoyID lock args are 22 bytes when quoting capacity
- Count only empty, typeless lock cells as spendable balance
- DAO compensation must use the deposit cell's occupied capacity (102 CKB), not 61
引用这条经验
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.