BIP 45 Deterministic P2SH Multisignature Wallets Explained

BIP 45 Deterministic Multisig Wallets: This guide explains BIP 45 Structure for Deterministic P2SH Multisignature Wallets in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.

Shared-wallet objective

An m-of-n group needs every participant to derive the same receive and change scripts while retaining independent signing keys. BIP 45 standardised branches, cosigner ordering and address indexes so address generation could be offline from other parties. Transaction proposal and signature exchange still required communication.

Purpose and cosigner branch

The hierarchy uses a hardened purpose branch and assigns each participant a cosigner index. Cosigners sort or agree the public-key material according to the specified process. A different ordering changes the redeem script and P2SH address even when the same people and threshold are involved.

Receive-address derivation

For a receive address, each wallet derives the relevant public child for every cosigner, assembles the m-of-n multisignature redeem script and hashes it into P2SH. Every party should independently reproduce and verify the address before it is supplied to a payer. One coordinator display is insufficient for high-value deposits.

Change branch

Change derivation identifies the cosigner creating the proposal and uses a distinct branch. All signers must recognise the expected change script and refuse an unknown output. Malware that substitutes change can produce a technically valid transaction that every inattentive signer authorises.

Signing workflow

The creator prepares a transaction proposal and sends it to cosigners, who decide whether to sign. BIP 45 predates PSBT, so modern software may not exchange the historical format directly. Signers still need UTXO value, full outputs, fees, redeem scripts and derivation evidence on trusted displays.

Discovery and gaps

Each cosigner branch and address sequence needs discovery. Scanning only one participant or only external addresses can miss funds. Large unused ranges slow recovery and may exceed wallet defaults. A complete backup contains the quorum policy, every xpub, ordering, highest indexes, change rules and wallet birthday.

Modern migration

Export the full public policy and compare derived addresses in an isolated wallet before moving funds. Build a supported descriptor and PSBT workflow, verify every cosigner device and sweep through a jointly approved transaction. Do not assume that importing the same xpubs recreates historical ordering or script wrappers.

Conclusion

BIP 45 made deterministic multi-party P2SH derivation reproducible, but safe recovery needs the complete cosigner policy, ordering and discovery state. Modern descriptor and PSBT tooling should be adopted only after exact address equivalence is proven.