Multisig hardware wallets: how M-of-N works and who supports it

A multisig (multi-signature) wallet locks coins to several keys and a threshold: M of the N keys must sign before anything moves. BIP-383, the Bitcoin standard for describing multisig scripts, writes it as multi(k, KEY_1, ..., KEY_n), where k is the number of keys that must sign. Each key normally sits on a different device.

What is a multisig wallet?

With independent keys and a threshold above one, it removes dependence on a single signing key. In a single-signature wallet, whoever holds the recovery phrase (and the passphrase, if one is set) controls the coins. In a 2-of-3 multisig, a thief needs two keys, and you can still spend if one device or backup is lost. Trezor’s multisig guide gives the common shapes: 2-of-3, where “any two of them” can send, and 3-of-5.

The price is more to look after: N signing keys, a recovery plan for each, and a record of how the keys fit together. Lose more keys than the threshold allows and the coins cannot be moved.

What does a hardware wallet do in a multisig?

It signs; it usually does not build the wallet. BIP-129, a cross-vendor setup standard, splits the work into two roles. The coordinator is the software that “determines what type of multisig is used” and collects each signer’s extended public key (xpub). A signer is “any software or hardware that controls the private keys”. Sparrow, Electrum and Specter are coordinator apps; Casa and Unchained run coordinator services. Unsigned transactions travel between them as PSBTs (BIP-174), so each signer can add its signature, even while offline.

The danger BIP-129 names is a tampered setup: an attacker who changes the configuration can dupe you “into sending funds to the wrong address”. The defence is registration: you check the wallet policy on the device’s screen once, and from then on the device recognises that policy and verifies addresses itself. Ledger registers a policy only after the user confirms it “with the secure screen”, and it does not keep the whole wallet: the device returns an HMAC (a cryptographic tag) that the coordinator stores and presents again, so “the Ledger doesn’t need to store the entire multisig wallet on the device” (2023 post). BitBox lists “Register multisig account with device”; COLDCARD imports a wallet setup file and tells users to “cross-verify multisig addresses with your coordinator software”.

Which hardware wallets support multisig, and with which coordinator?

Grouped by how the makers implement it:

Coordinator built into the maker’s app. Bitkey is a multisig by design: a built-in 2-of-3 with one key on the hardware, one in the phone app and one on Bitkey’s server, and no seed phrase. Blockstream Jade Plus offers a “Multisig Shield” policy in the Blockstream app and works with Sparrow and Electrum. Since March 2026, Blockstream says, Jade can also serve “as a key within Unchained’s collaborative 2-of-3 multisig custody vaults” (Q1 2026 update).

Signer for named third-party coordinators.

• Ledger Nano S Plus, Nano X, Flex and Stax: Bitcoin multisig through the Bitcoin app. Ledger’s guidance names Sparrow for its devices in general, and its posts also name Unchained and Caravan; we found no model-by-model coordinator list for the Flex and Stax.
• Trezor Safe 3, Safe 5, Safe 7, Model One and Model T: Trezor Suite “doesn’t support multisig wallets directly”; Trezor names Electrum, Sparrow and Casa (a paid service).
• BitBox02 Nova Multi: Electrum, Sparrow and Specter.
• Keystone 3 Pro: Sparrow. Keystone says its team co-authored BIP-129.
• COLDCARD Mk5 and COLDCARD Q: Electrum, or a wallet built on the devices themselves, with up to 15 co-signers.
• OneKey Pro: Sparrow for Bitcoin, plus Safe on Ethereum and Squads on Solana.
• KeepKey: Electrum.

Safe and Squads are not Bitcoin scripts but on-chain accounts on Ethereum and Solana whose rules the network enforces; the hardware wallet signs as one owner.

Advertised, coordinator not named. Foundation lists Bitcoin multisig and collaborative custody for Passport Prime without naming coordinators. Ledger Nano Gen5 appears on the supported-device list for Ledger Enterprise Multisig; we found no Gen5-specific guidance for personal coordinators.

No multisig in the maker’s app. In a June 2024 AMA Tangem said it “will not implement multi-sig algorithms” in its wallet and pointed to on-chain options such as Gnosis Safe, which covers the Tangem Wallet and Tangem Ring. Arculus says the Arculus card “is not a multisignature (multisig) wallet”, but that “you can use WalletConnect and Safe” to make one, with the card’s address as an owner; that is an on-chain Safe account, not Bitcoin multisig. For the ELLIPAL Titan 2.0, SafePal S1 Pro, SafePal X1 and NGRAVE ZERO, we found no statement of device multisig support.

How do you back up a multisig wallet?

Back up the wallet’s configuration as well as each seed. Recovery phrases alone do not record which keys belong together, the threshold or the script type. COLDCARD’s documentation says multisig wallets “can be reconstructed from the seed words, but the M-of-N policy, co-signer XFP/XPUBS, derivation path and address type must be known”. Trezor warns that without the xpubs “you will not be able to send a transaction”, even with every private key, and asks you to back up the xpub of every key in the set.

The portable form of that record is an output descriptor (BIP-380): one line of text with the script type, threshold, xpubs and derivation paths. The standard says descriptors allow “wallet backups and exports which specify the exact scripts”. OneKey’s Sparrow multisig guide asks you to save the configuration file and descriptor as soon as the wallet is created. A descriptor exported with xpubs only holds no private keys (BIP-380 also allows descriptors that contain them, so check what you export), but BIP-129 notes that whoever learns the configuration can monitor the wallet’s transactions, so keep copies offline, one with each seed backup. Bitkey is the exception: it has no seed phrase, and recovery runs through its own three keys.

Is there a best multisig wallet?

No device leads on every criterion. These questions separate them:

• Does your coordinator list the device? Each coordinator names a different set of devices.
• Does the device register the wallet, so it can check addresses on its own screen? Ledger, BitBox and COLDCARD document registering or importing the wallet setup.
• Can you mix makers? Sparrow’s best practices recommend at least 2-of-3 and “hardware wallets from multiple vendors”, so one vendor’s flaw cannot compromise the whole setup.
• Are the seeds independent? Coinkite says each cosigner “should use an independently generated seed”, and that several passphrase wallets made from one COLDCARD seed “share one parent-seed failure domain”.

Multisig also does not stop signers approving a transaction they cannot read. On 21 February 2025 the exchange Bybit lost “almost $1.5 billion” from one of its Ethereum multisig cold wallets; its forensic update says attackers who had compromised Safe{Wallet} infrastructure could “deceive signers into approving a malicious transaction” (more in what is a cold wallet).

What we could not verify

• Blockstream’s “Multisig Shield”: the Jade FAQ names it without saying which keys it uses or who holds them.
• Personal-coordinator support for the Ledger Nano Gen5, model-specific coordinator support for the Ledger Flex and Stax, and the coordinators that work with Passport Prime.
• Bitkey’s product page and BitBox’s Bitcoin-only page blocked our direct fetches on 14 and 15 October 2026; their rows rest on the quotes recorded in our dataset.
• Arculus’s Safe route: the maker documents the WalletConnect steps; we have not tested it or confirmed which networks it covers.
• Compatibility by firmware or coordinator version. We have not tested any integration.