Three independent signing devices placed on separate mats, with two screens illuminated, editorial illustration
BIP 129 / MULTISIG

Agree on the same multisig wallet.

Bitcoin Secure Multisig Setup specifies how participants exchange and verify a shared wallet configuration.

Read the explanation
← All standards

Why it exists

BIP 129 standardises the exchange of multisig wallet information before funds are received. Its Bitcoin Secure Multisig Setup format helps a coordinator and independent signing devices agree on the same keys, threshold and script policy, rather than relying on an unverified configuration file.

How it works

Each signer provides a key record containing its public key or extended public key, origin information, a description and a signature. The coordinator validates the records and assembles a descriptor record. Optional encrypted exchange uses setup-session secrets to protect the records in transit.

The coordinator sends the assembled record back to every signer. Each signer must check its exact key is included, verify the policy and derivation restrictions, and show the first address and policy parameters for confirmation. A matching four-byte fingerprint alone is insufficient to prove that the correct key is present.

PUT IT IN CONTEXT

A practical example

For a two-of-three wallet, three devices export their records. The coordinator constructs a policy requiring any two signatures. Before the first deposit, each participant confirms that the same three keys and two-signature threshold produce the same first receive address. An unexpected fourth key or different threshold is a setup failure.

What to keep in mind

BSMS does not make a compromised signer trustworthy or decide where keys should be stored. Tamper-resistant storage and later receive/change-address verification remain responsibilities of the signer. Backups still need the complete wallet configuration as well as enough private keys.

Status & implementation

BIP 129 is Complete as an application specification. Its exchange format requires compatible coordinator and signer support; PSBT support alone does not establish BSMS support. No Bitcoin consensus activation is required to exchange these records.

Specification status: Complete · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close