Why it exists
BIP 48 standardizes where deterministic multisig wallets obtain cosigner keys. It adds a script-type level to the account hierarchy, allowing the same signer to keep distinct branches for nested-SegWit and native-SegWit multisig accounts.
How it works
The path has six levels: purpose, coin, account, script type, receiving or change, and address index. Purpose is 48'; mainnet coin type is 0'. Script type 1' selects nested SegWit and 2' selects native SegWit. The first four levels are hardened.
Every cosigner supplies public-key information for the agreed account. For each address index, the coordinator derives the participant keys and sorts their compressed encodings according to BIP 67 before constructing the multisig script. The threshold and all cosigner keys determine the shared wallet.
A practical example
A native-SegWit mainnet multisig account can use m/48'/0'/0'/2' on each signer. Its first receiving keys are derived at /0/0. A 2-of-3 policy then combines the three corresponding public keys into one spending script requiring two signatures.
What to keep in mind
Two seed backups alone do not describe a 2-of-3 wallet completely: recovery still needs the third cosigner public key, threshold, script type and derivation information. A signer using the wrong account branch can produce valid keys for a completely different wallet.
Status & implementation
The specification is Deployed and explicitly records established m/48' usage. It covers the named SegWit multisig script types; it is not a universal convention for every Taproot or MuSig2 wallet. Confirm matching exports before funding.
Specification status: Deployed · Sources checked 13 November 2026
