iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
An m-of-n wallet requires a defined minimum of m signatures from a set of n keys to authorize an action. That spreads authorization across keys, but it does not make a wallet safe by itself: the policy must be configured correctly, independently checked, supported by the signers, and recoverable along with the keys.
What does m-of-n mean?
In a threshold policy, n is the number of authorized keys and m is the minimum number of signatures required. In Bitcoin descriptor notation, multi(k,KEY_1,...,KEY_n) expresses that policy: at least k of the listed keys must sign, and k cannot be greater than the number of keys. BIP 383 defines sortedmulti() as sorting keys lexicographically in the resulting script, while multi() retains descriptor order. That ordering distinction is part of the policy representation, not a cosmetic label.
A threshold answers one question—how many keys must authorize—but not who controls them, whether their devices fail independently, whether the configured keys match the intended participants, or whether the wallet can be reconstructed later. Those are separate design and verification questions.
Free tools Windows power users keep installed
One-click scans. No signup required.
How Bitcoin and Ethereum multisig differ
| Concern | Bitcoin script multisig | Ethereum contract-account multisig |
|---|---|---|
| Where authorization is enforced | In the Bitcoin output script described by the wallet policy. | In contract code associated with the contract account. |
| What the threshold describes | A required number of listed keys to satisfy the script policy; descriptor notation can express the threshold and keys. | A required number of owner confirmations in the account’s authorization pattern; the contract’s code and configuration define the behavior. |
| What must be checked beyond owners and threshold | Descriptor, key origins, derivation restrictions, key ordering, and the derived receiving address. | Contract configuration and any extensions that may add alternate execution paths, including modules and delegatecall-loaded logic. |
| Recovery information | Seeds plus the wallet policy or descriptor and the information needed to derive and identify keys. | Private keys alone do not describe contract behavior; retain the relevant account configuration and understand the contract’s code and extensions. |
Ethereum’s account documentation distinguishes externally owned accounts, which are controlled by private keys, from contract accounts, which are controlled by code. A wallet is an interface for interacting with either type; the interface does not change where authorization is enforced. Safe’s smart-account overview describes threshold owner confirmations as its default authorization pattern, but also describes modules that can introduce alternate execution paths. Treat the threshold-owner check and the extension surface as separate parts of a security review.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
How to build and verify a Bitcoin multisig policy
Bitcoin Core documents a descriptor-wallet and PSBT workflow. Its signet tutorial illustrates a 2-of-3 setup; this is an example workflow, not a universal compatibility guarantee or a recommendation that 2-of-3 suits every use case.
- Create separate participant wallets and collect their public keys. The tutorial creates three participant wallets and derives an extended public key from each. Keep private keys with their intended signers; the coordinating wallet can be watch-only.
- Construct the descriptor. The tutorial builds a
wsh(sortedmulti(2,...))descriptor from the three keys, then calculates its descriptor checksum. Its own warning says the derivation setup is illustrative and does not conform to BIP 45 or BIP 87. Do not treat the example’s derivation choices as a general standard. - Import the policy into a watch-only wallet. Bitcoin Core’s descriptor documentation describes importing the descriptor into a wallet that can derive addresses and create unsigned transactions without holding the participants’ private keys.
- Compare the setup before receiving funds. Verify that each participant’s expected key is present in the descriptor and that participants independently derive the same receiving address. Check the policy itself, not only a displayed threshold or address.
- Coordinate spending with PSBTs. A partially signed Bitcoin transaction can be passed among signer wallets for signature collection, then finalized and broadcast through a compatible workflow. Each signer still needs to verify the transaction details it is approving.
For hardware or other external signers, Bitcoin Core recommends including key-origin information—the master-key fingerprint and derivation steps—in the descriptor. The documentation also recommends comparing receiving addresses among participants. It cautions that signer behavior can differ and that the quick-start workflow has privacy limitations. Hardware-wallet status alone does not establish support for a particular descriptor, derivation path, coordinator, or transaction review behavior.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
What every signer should verify
A coordinator may collect keys and assemble the policy, but each signer should confirm that the resulting record matches the agreement. BIP 129’s setup model calls for the signer to verify that their key appears in the descriptor and to persist the descriptor record. It also specifies displaying the first address and policy information so the signer can check the configuration.
- Threshold and participant count: confirm the intended M-of-N policy rather than relying on a short label.
- Key identity and position: check that the signer’s key is present and note its position in the policy.
- Derivation restrictions: verify the paths or other derivation constraints the policy permits.
- Receiving address: compare the first derived address across participants and, before use, verify the address through the signer’s own supported interface where available.
- Transaction destination and amount: inspect what the transaction does on the signer’s device or other trusted review path; a valid threshold does not prove that the transaction is intended.
- Policy record: save the descriptor and associated setup information in a form that can be checked and recovered later.
BIP 129 specifically identifies the first address, M, N, derivation restrictions, and the signer’s key position as policy details to display during setup. These checks reduce the risk of participants approving a policy different from the one they intended.
Rank #3
- All your digital assets in one place. You can manage thousands of crypto including Bitcoin, Ethereum, Solana, Tether and more.
- Defend your identity against hackers: secure your online accounts with passwordless, hardware backed, 2FA logins for all your favorite apps and websites.
- Connectivity: USB-C cable connection only. No Bluetooth.Compatible with the Ledger Wallet crypto app, both desktop (Windows, macOS, Linux) and mobile (Android only). Not compatible with iOS.
- Protect your digital assets with the industry's best security: keep your private keys offline in your private signer, battle-tested by the Donjon's white hat hackers, CC EAL 6+ certified Secure Element, constantly updated Ledger OS.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
What to back up besides seed phrases
A seed phrase may restore a signer’s keys without restoring a nonstandard multisig wallet policy. The policy determines which keys participate and how addresses are derived. If it is missing, reconstructing the intended wallet can be difficult or impossible. BIP 388 warns that losing the wallet-policy backup can cause permanent loss of funds.
- Preserve the complete descriptor or equivalent wallet-policy record, including its checksum when applicable.
- Keep key-origin information, derivation restrictions, and the mapping between participants and keys.
- Document the threshold, network, and any coordinator or signer assumptions needed to reconstruct the setup.
- Keep recovery information separate from any single signer device, while protecting it against unauthorized access.
- Test recovery with the actual backup and compatible software before relying on it; confirm that it reconstructs the expected policy and receiving addresses.
Do not assume that a seed backup is a complete wallet backup. Test the policy backup as well as the ability to restore individual signers.
Rank #4
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
What can go wrong with signer or coordinator compatibility?
A multisig setup depends on more than the keys. The coordinator, wallet-policy format, network, derivation choices, and signer capabilities must work together. Bitcoin Core’s example is a tutorial, and its documentation notes that external signer behavior may differ; a device should not be presumed to support every descriptor or to display the same transaction details as another signer.
- A signer rejects the descriptor: check whether it supports the exact script type, key-origin format, and derivation path in use. Do not silently substitute a different policy.
- Participants derive different addresses: stop before receiving funds. Compare the descriptor, key order or sorting behavior, derivation information, network, and checksum, then independently derive the address again.
- A device cannot review the transaction as expected: establish what the signer actually displays and what it can verify. If the transaction cannot be independently reviewed to the required standard, do not treat successful signing as proof of safety.
- The coordinator is unavailable: use the preserved policy and an alternative compatible workflow only if it can reproduce and verify the same policy. Practice this recovery path before funds depend on it.
- Ethereum extensions are present: review modules, guards, fallback behavior, and any delegatecall-loaded logic as part of the account’s authorization surface; owner threshold alone may not describe every route to execution.
Choosing a threshold without overpromising security
There is no universally safest threshold. A higher m can make unauthorized approval harder if keys are genuinely independent, but it also makes routine signing and recovery more dependent on signer availability. A lower threshold can improve availability while concentrating more trust in fewer keys. Evaluate the policy against the likely loss, compromise, and unavailability scenarios—not just the number of keys.
Quick Recap
Best Value
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
- Identify who controls each key and whether any person, device, organization, or location controls multiple keys.
- Decide what happens if one key is compromised, lost, delayed, or permanently unavailable.
- Confirm that remaining signers can meet the threshold using the documented recovery process.
- Review setup and transaction verification as carefully as the threshold number.
- For contract accounts, include code and extensions in the policy review rather than treating owner confirmations as the entire authorization model.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
