HDM (Multi-Signature HD Wallet)
Combines HD derivation with multisig, so each cosigner has an extended key tree for multiple accounts or addresses.
HDM (Hierarchical Deterministic Multisig) is the standard architecture for modern Bitcoin multisig: each cosigner uses their own HD wallet seed, and the multisig wallet is described by the combination of all cosigners' extended public keys (xpubs) plus the threshold (e.g., 2-of-3).
Why this is the right design:
- Each cosigner's HD seed produces many addresses. The multisig wallet inherits this: rather than generating one multisig address per setup, the wallet derives a sequence of addresses indexed by
m/.../0/iwhereiranges over all receive indices. Same privacy / fresh-address discipline as single-sig HD wallets. - xpubs only need to be shared once. During wallet setup, each cosigner exports their xpub. The combined wallet descriptor (e.g.,
wsh(sortedmulti(2, xpub_A/.../<0;1>/*, xpub_B/.../<0;1>/*, xpub_C/.../<0;1>/*))) covers all future addresses. - Each signer's keys remain isolated. Cosigner A's seed never touches Cosigner B's device. Each signs only with their own key, locally.
- Backup is one seed per cosigner. If Cosigner A loses their device but has their seed backed up, they can restore. If they lose both, the other cosigners can still recover their cosigner-share via remaining xpubs + multisig threshold (assuming the lost cosigner's keys aren't required to meet quorum).
Real-world deployment patterns:
- 2-of-3 personal custody. One cosigner on a hardware wallet at home, one at a safe deposit box or with a trusted family member, one with a service like Unchained or Casa as the "always-available" third.
- 3-of-5 institutional. Standard corporate treasury setup. Five cosigners spread across executives or geographic offices; three required to spend.
- 2-of-2 Lightning channels. Every Lightning channel is technically HDM (2-of-2) under the hood, with each channel partner's keys derived from their HD seed.
The convention is now standardized via BIP-48 which specifies derivation paths for multisig wallets, and via the descriptor wallet format that captures the full multisig setup in a portable string.
What HDM doesn't simplify: setup ceremonies (you still need to securely exchange xpubs at setup time), inheritance planning (each cosigner's seed needs its own succession plan), and recovery testing (the more cosigners, the more rehearsal needed). But the standard makes operating multisig wallets meaningfully more practical than the pre-HD-multisig days when each cosigner had to back up individual private keys.
Key takeaways
- Deploys multiple HD seeds in a single multisig arrangement
- Each cosigner's extended keys generate coordinated addresses
- Improves security, redundancy, and scaling for multi-signature wallets