BIP 129 BSMS guide covering its Complete status, coordinator and signer roles, two-round setup, key records, descriptor templates, proofs, encryption and tests.
This guide explains BIP 129 Bitcoin Secure Multisig Setup (BSMS) in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 129 Bitcoin Secure Multisig Setup (BSMS): The coordinator distributes setup parameters and each signer returns a key record with origin and extended public-key information plus the required proof.
A node operator is checking BIP 129 Bitcoin Secure Multisig Setup (BSMS). Every signer verifies threshold, membership, script, network, derivations and its own key before persisting the same configuration.
The BIP is Complete, Applications and Specification, requiring BIP32, BIP322 and output descriptor standards. Pin supported modes and revision across every participant.
A coordinator assembles the wallet policy and signer records; signers create and authenticate their own contributions and validate the final configuration. The coordinator is not automatically trusted with keys.
The coordinator distributes setup parameters and each signer returns a key record with origin and extended public-key information plus the required proof. Authenticate the session and expected participant out of band.
The coordinator constructs and distributes the descriptor template. Every signer verifies threshold, membership, script, network, derivations and its own key before persisting the same configuration.
BSMS defines no-encryption and encrypted modes with session tokens and derived encryption keys. Encryption protects transport content but does not authenticate a malicious coordinator by itself.
Store the final descriptor or template, signer origins, threshold, script type and network alongside each independent seed backup. A seed alone cannot reconstruct an arbitrary multisig wallet.
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
BIP 129 Bitcoin Secure Multisig Setup (BSMS): The coordinator distributes setup parameters and each signer returns a key record with origin and extended public-key information plus the required proof.
The BIP is Complete, Applications and Specification, requiring BIP32, BIP322 and output descriptor standards.
A coordinator assembles the wallet policy and signer records. Signers create and authenticate their own contributions and validate the final configuration.
The coordinator distributes setup parameters and each signer returns a key record with origin and extended public-key information plus the required proof.
BIP 129 turns multisig setup into a reviewable interoperable ceremony. Its protection comes from each signer independently verifying and storing the same authenticated descriptor policy, not from coordinator convenience.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
BIP 450 guide to Draft Formosa themed mnemonic stories, entropy and checksum mapping, theme JSON, BIP39 conversion, passphrases and recovery safety.
BIP 393 guide to Draft descriptor annotations for birth height, gap limit and Silent Payment max label, checksum rules, parsing and recovery safety.
BIP 392 guide to Draft sp() descriptors, spscan and spspend encodings, watch-only and full-wallet forms, key origins, recovery and validation.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.