All lessons · Wallets and signing · Start here · Glossary
secp256k1_blake160_multisig_all signature matching rulesWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-19
The system multisig lock (secp256k1_blake160_multisig_all) expects the witness to carry exactly M signatures (threshold), uses each member key at most once, and requires all of the first R keys (require_first_n) to be among them. A tool collecting partial signatures should dedupe per member key and check the first R are present before finalizing, since any M valid distinct signers that include the first R form a complete set.
Why it matters: A collector that counts a repeated key's signature twice, or finalizes without all first R members, builds a witness the multisig lock rejects at verification.
Pattern
complete: thresholdMet && firstRPresent,- Concepts
- Witnesses and signatures
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-08
- Last changed
- 2026-11-08
- 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-11-08 · ILE-Labs/ckb-msig · more from this project
More about Wallets and signing
- JoyID sub key membership is checked through the CoTA aggregator
- JoyID sub key signatures depend on the live CoTA cell dep holding the sub key root
- Devnet tests need a real secp256k1 lock to exercise signing
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "secp256k1_blake160_multisig_all signature matching rules", CKB lessons, https://pulse.lusocryptolabs.com/learned/wallets/secp256k1-blake160-multisig-all-signature-matching-rules, CC BY 4.0, last changed 2026-11-08.