Stackexchange iconStackexchangeSep 23, 2026

Multisig wallet with Bitcoin Core and hardware wallets

Imagine a multisig wallet with cosigners comprising say 2 (software) Bitcoin Core wallets, and 3 hardware signing devices, in a m-of-5 multisig setup. Core's m/84'/0'/0'/0/* xpub with hardware wallets' m/48'/0'/0'/2' BIP-48 derivation paths.

Share this story

Send the public story page.

Useful takeaways from this story.

Imagine a multisig wallet with cosigners comprising say 2 (software) Bitcoin Core wallets, and 3 hardware signing devices, in a m-of-5 multisig setup.

Core's m/84'/0'/0'/0/* xpub with hardware wallets' m/48'/0'/0'/2' BIP-48 derivation paths.

I understand that coordination software won't care about different paths to derive receive address, but could there be other issues, long-term?

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

Imagine a multisig wallet with cosigners comprising say 2 (software) Bitcoin Core wallets, and 3 hardware signing devices, in a m-of-5 multisig setup. Core's m/84'/0'/0'/0/* xpub with hardware wallets' m/48'/0'/0'/2' BIP-48 derivation paths. I understand that coordination software won't care about different paths to derive receive address, but could there be other issues, long-term?

How it works

  • I do understand we can simplify things with just m/84 or m/48 paths within the multisig, but question is about mixing paths.

What to take from it

Do experienced bitcoiners foresee a problem with this setup?

Details worth keeping

Specifically, the wsh(sortedmulti(..)) descriptor will mix address paths.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app