Guides / Set up / Multisig wallet software
Set up

Multisig wallet software for a company

The coordinator is the app that ties the signers together, builds the transactions and holds the wallet setup you also need to back up. This page explains what that software does, what to keep besides the recovery words, how it fits the key ceremony and the recovery drill, and compares four open source options on facts only.

Education onlyNo endorsementChecked 21 Nov 2026

Sources checked 21 November 2026. This page is about the coordinator app used with a company multisig. It is education, not legal, tax or investment advice, and it does not recommend any product. The facts here do not differ between the UK and the US, so there is no country jump. If anything here conflicts with a linked source, the source wins. Confirm the current documentation for any app you use, and test recovery before any real funds are sent.

Short answer

The coordinator, sometimes called the wallet software, is the app that holds a watch-only view of the company wallet, builds the unsigned transactions, and collects signatures from the hardware signers. It also stores the wallet configuration: the public keys, the threshold (for example 2 of 3) and the script type.

The recovery words for each key are not enough on their own. A multisig also needs a backup of that configuration, usually as an output script descriptor, a BSMS file, or the coordinator's own wallet file. Two recovery phrases without that record are not always enough to rebuild the wallet, because the other public keys and the exact set-up would be missing.

What to back up besides the recovery words

A single key wallet can often be rebuilt from its recovery phrase alone. A company multisig cannot be treated that way. To find and spend the funds, wallet software needs to know every public key in the set, the threshold and the script type. That information lives in the wallet descriptor, the short text record defined in BIP 380.

Source: Bitcoin BIPs: BIP 380: Output script descriptors, general operation (wallet backups and exports).

Some coordinators also export a Bitcoin Secure Multisig Setup (BSMS) file, defined in BIP 129, or their own wallet file. The idea is the same: keep a copy of the configuration with every key backup. The descriptor or configuration file cannot move funds, but anyone who reads it can see the wallet's balance and history, so store it with the same care as company bank details.

Source: Bitcoin BIPs: BIP 129: Bitcoin Secure Multisig Setup (BSMS), a common configuration file for registering and backing up a multisig wallet.

Our steel backups guide covers where each copy should live. The descriptor is usually too long to stamp by hand, so it is kept as a printed sheet, a QR code, or a file on an encrypted drive, sealed with each key backup and also kept in the company records.

How it fits the key ceremony

The coordinator is typically where the wallet is first created. Each signer's extended public key is imported, the policy and script type are set, and the first receiving address is checked on every signing device before any funds are sent. The descriptor or configuration file is then exported and backed up as part of the same sitting.

Where the software allows it, that first build and the first test transaction can be done on testnet, so a mistake is cheap. The walkthrough of the sitting itself is on the key ceremony guide. This page is only about the app that ties those steps together.

How it fits the recovery drill

In the yearly recovery drill, the coordinator is the app you use to prove the set-up still works. A typical drill loads a watch-only wallet from the descriptor copy, checks that the first receiving address still matches the ceremony record, builds a small test transaction, and collects signatures from the chosen pair of keys.

It is also what you would use if a laptop were lost. The keys, their backups and the descriptor are what matter. The original computer, and even the company's node, can be replaced. If the descriptor copy cannot rebuild a watch-only wallet that shows the expected address, that is a drill failure to fix before any emergency.

Four open source options, compared on facts only

The four apps below are listed in alphabetical order. Inclusion only means each project publishes its source and official documentation that could be checked on 21 November 2026. It is not a ranking, a recommendation or a buying guide. Each row is a fact taken from that project's own site or documentation.

AppWhere it runsHow the wallet setup is backed upHow signatures are collected
ElectrumWindows, macOS, Linux and Android, plus a command line and daemonEach cosigner keeps its seed, and the wallet is built from the other cosigners' master public keys; the wallet file holds that setupA partly signed transaction is passed by file, QR code, or the Cosigner Pool plugin
LianaDesktop, with a separate daemonExport the output script descriptor and back it up as well as the seeds; the project says recovery is not possible without the descriptorThe policy is registered on each signing device; transactions follow the primary path, or a recovery path once its timelock has matured
NunchukMobile and desktop, with a command line tool as wellA BSMS configuration file (BIP 129), plus the seeds for enough keys to meet the thresholdSignatures on the device, including air-gapped flows over QR codes or SD cards, and collaborative flows for multi-user wallets
SparrowDesktop (Windows, macOS and Linux)The wallet can be created or edited from an output descriptor; the encrypted wallet file holds the policy, script type and keystoresSignatures are collected in a PSBT, over USB or an air-gapped flow, including QR codes

Electrum

Electrum is a free, open source, self-custodial bitcoin wallet that has been in continuous development since 2011. The project says electrum.org is the only official website. It runs on Windows, macOS, Linux and Android, and also has a command line and a daemon with a JSON-RPC interface.

Source: Electrum: Official website: Electrum is a free, open source, self-custodial bitcoin wallet, in continuous development since 2011; electrum.org is the only official website.

A multi-signature wallet is created from File, then New, then Multi-signature wallet. Each cosigner shares its master public key so that every wallet is built from the same set. The official tutorial walks through a 2 of 2 example. To spend, one wallet creates and signs a transaction, and that partly signed transaction is passed to the next signer as a file, as a QR code, or through the Cosigner Pool plugin, which encrypts the payload to the cosigner's master public key.

Source: Electrum: Official documentation: Multisig wallets, including a 2 of 2 example, exchanging master public keys, and passing a partly signed transaction by file, QR code or the Cosigner Pool plugin.

Electrum also documents a cold storage pattern: a watching-only wallet on an online machine, built from a master public key, and an offline wallet that signs an unsigned transaction file. Hardware wallets are supported through official plugins.

Source: Electrum: Official documentation: Cold storage, including a watching-only wallet from a master public key and signing an unsigned transaction file on an offline machine.

One fact that matters at a company key ceremony: new Electrum wallets use Electrum's own seed format by default, not BIP39. Electrum can restore BIP39 seeds, but seed phrases are not automatically portable between wallet applications. If a company might later rebuild the wallet in a different coordinator, that difference needs to be recorded and tested, not assumed.

Source: Electrum: Official documentation: Electrum seed phrases, including how Electrum's default seed format differs from BIP39, and that seed phrases are not automatically portable between wallet applications.

Liana

Liana is an open source bitcoin wallet from Wizardsardine, released under the BSD 3-Clause licence, with official documentation at lianawallet.com and source at the wizardsardine/liana repository. Unlike a fixed threshold alone, a Liana wallet has a primary spending path that can sign at any time, and one or more recovery paths that become available only after a period of inactivity. The delay is enforced on-chain by a relative timelock. Either path may contain one key or several keys as a multisig.

Source: Wizardsardine: Liana repository: an open source bitcoin wallet (BSD 3-Clause) with a primary spending path and one or more recovery paths that become available after a period of inactivity; either path may be a multisig, Liana: Official website.

That recovery-path design is why Liana appears on this list next to ordinary threshold coordinators. A company that wants a delayed fallback, as described on our timelocked recovery page, is looking at this kind of policy, not only a 2 of 3 that never changes.

The official usage guide says you must back up both the output script descriptor and the private keys, and that without the descriptor you will not be able to recover from your backup. A person who obtains the descriptor could learn the balance and history, but could not spend. The official set-up guide adds that the descriptor should be registered on each signing device, and exported from Settings, then Wallet, then Export descriptor. It also says the descriptor can be stored encrypted, so copies can be kept in more places than a seed would ever be stored.

Source: Wizardsardine: Liana USAGE.md: back up the output script descriptor and the private keys; without the descriptor you will not be able to recover from your backup; a person who has the descriptor can learn the balance and history but cannot spend, Liana: Official guide: How to set up your first Liana wallet, including registering the descriptor on each signing device and exporting it from Settings, then Wallet, then Export descriptor.

This site discusses company treasuries as a multisig, typically 2 of 3. Liana can be configured with a single key in a path; that is a fact about the software, not a suggestion to use a single key for company funds.

Nunchuk

Nunchuk is a bitcoin multisig app whose official site is nunchuk.io, with documentation at resources.nunchuk.io and source under the nunchuk-io organisation on GitHub. The official site describes self-custody multisig, assisted multisig and multi-user collaborative wallets, support for hardware signers, and air-gapped signing with QR codes or SD cards.

Source: Nunchuk: Official website: self-custody, assisted and multi-user collaborative multisig, hardware wallet support, and air-gapped signing with QR codes or SD cards, Nunchuk: nunchuk-io organisation on GitHub, including the open source client and library repositories.

When you create a multi-signature wallet, Nunchuk prompts you to back up a BSMS file. Its documentation says you will need either that file plus enough keys to meet the threshold, or all of the keys and a reconstruction of the original configuration, and that the second route can fail for a highly customised wallet. If you have neither a backup nor a working wallet, it says you risk losing access to the funds. The BSMS file contains information about the wallet only: it can be used to track the funds, but not to spend them.

Source: Nunchuk: Official documentation: Creating a multi-signature wallet, including the prompt to back up a BSMS file, and the warning that you need the configuration file plus enough keys, or all keys and a reconstruction of the original setup, Bitcoin BIPs: BIP 129: Bitcoin Secure Multisig Setup (BSMS), a common configuration file for registering and backing up a multisig wallet.

Official recovery guides for a collaborative wallet, and for recovery with Bitcoin Core, both start from the same two ingredients: the seed phrases for enough keys to meet the threshold, and the wallet configuration file defined in BIP 129.

Source: Nunchuk: Official documentation: Collaborative wallet recovery, which requires the seed phrases for enough keys to meet the threshold, plus the wallet configuration file, Nunchuk: Official documentation: Wallet recovery using Bitcoin Core, which requires the seed phrases and the wallet configuration file defined in BIP 129.

Sparrow

Sparrow is a desktop bitcoin wallet for Windows, macOS and Linux. The official site is sparrowwallet.com. The project's FAQ says it is licensed under Apache 2, which it describes as open source, and points to the sparrowwallet/sparrow repository. It is not browser based. It has been built around the Partially Signed Bitcoin Transaction (PSBT) format.

Source: Sparrow Wallet: FAQ: the project is licensed under Apache 2, which it describes as open source, and points to the sparrowwallet/sparrow repository, Sparrow Wallet: sparrowwallet/sparrow repository on GitHub, Bitcoin BIPs: BIP 174: Partially Signed Bitcoin Transaction format (PSBT).

A Sparrow wallet has a policy type of single signature or multi signature, a script type, and one or more keystores. You can use connected or air-gapped hardware wallets, a software keystore, or a watch-only xpub. Official features include configuration from an output descriptor, import and export of Electrum wallets, USB and air-gapped signing (including QR codes), and the ability to run offline. For a view of the chain it can connect to a public Electrum server, to Bitcoin Core, or to a private Electrum server. Testnet is available from Tools, then Restart in Testnet.

Source: Sparrow Wallet: Features: a desktop wallet built around PSBTs, with single signature and multisig, watch-only xpub keystores, hardware wallets over USB or air-gapped methods, and configuration from an output descriptor; also import and export of Electrum wallets, Sparrow Wallet: Quick Start: every wallet has a policy type (single signature or multi signature), a script type and keystores; wallets can be created as connected or air-gapped hardware, a software wallet, or a watch-only xpub wallet; testnet is supported.

Sparrow publishes its own best practices page. For what it calls true cold storage, that page discusses a private Electrum server, a unique password on the wallet, at least a 2 of 3, hardware wallets from different vendors for a quorum, and storing those devices and their backups in different locations. Those are Sparrow's own words, not a recommendation from this site.

Source: Sparrow Wallet: Best Practices: for what Sparrow calls true cold storage, its own page discusses a private Electrum server, a wallet password, at least a 2 of 3, hardware wallets from different vendors, and storing them in different locations.

What this page does not do

This page does not pick a coordinator, and it does not recommend a single signature wallet for company funds. It does not say whether a company should run its own multisig or use a regulated custodian. Features change, so confirm the current documentation for every signer, script type, backup format and signing flow you plan to use, and test recovery on testnet or with a small amount first.

Read next

Sources

Primary sources only. Each link was checked on 21 November 2026. Rules change, so confirm the current version with your adviser.

  1. Bitcoin BIPsBIP 380: Output script descriptors, general operation (wallet backups and exports)
  2. Bitcoin BIPsBIP 129: Bitcoin Secure Multisig Setup (BSMS), a common configuration file for registering and backing up a multisig wallet
  3. Bitcoin BIPsBIP 174: Partially Signed Bitcoin Transaction format (PSBT)
  4. ElectrumOfficial website: Electrum is a free, open source, self-custodial bitcoin wallet, in continuous development since 2011; electrum.org is the only official website
  5. ElectrumOfficial documentation: Multisig wallets, including a 2 of 2 example, exchanging master public keys, and passing a partly signed transaction by file, QR code or the Cosigner Pool plugin
  6. ElectrumOfficial documentation: Cold storage, including a watching-only wallet from a master public key and signing an unsigned transaction file on an offline machine
  7. ElectrumOfficial documentation: Electrum seed phrases, including how Electrum's default seed format differs from BIP39, and that seed phrases are not automatically portable between wallet applications
  8. WizardsardineLiana repository: an open source bitcoin wallet (BSD 3-Clause) with a primary spending path and one or more recovery paths that become available after a period of inactivity; either path may be a multisig
  9. WizardsardineLiana USAGE.md: back up the output script descriptor and the private keys; without the descriptor you will not be able to recover from your backup; a person who has the descriptor can learn the balance and history but cannot spend
  10. LianaOfficial guide: How to set up your first Liana wallet, including registering the descriptor on each signing device and exporting it from Settings, then Wallet, then Export descriptor
  11. LianaOfficial website
  12. NunchukOfficial website: self-custody, assisted and multi-user collaborative multisig, hardware wallet support, and air-gapped signing with QR codes or SD cards
  13. NunchukOfficial documentation: Creating a multi-signature wallet, including the prompt to back up a BSMS file, and the warning that you need the configuration file plus enough keys, or all keys and a reconstruction of the original setup
  14. NunchukOfficial documentation: Wallet recovery using Bitcoin Core, which requires the seed phrases and the wallet configuration file defined in BIP 129
  15. NunchukOfficial documentation: Collaborative wallet recovery, which requires the seed phrases for enough keys to meet the threshold, plus the wallet configuration file
  16. Nunchuknunchuk-io organisation on GitHub, including the open source client and library repositories
  17. Sparrow WalletFeatures: a desktop wallet built around PSBTs, with single signature and multisig, watch-only xpub keystores, hardware wallets over USB or air-gapped methods, and configuration from an output descriptor; also import and export of Electrum wallets
  18. Sparrow WalletQuick Start: every wallet has a policy type (single signature or multi signature), a script type and keystores; wallets can be created as connected or air-gapped hardware, a software wallet, or a watch-only xpub wallet; testnet is supported
  19. Sparrow WalletBest Practices: for what Sparrow calls true cold storage, its own page discusses a private Electrum server, a wallet password, at least a 2 of 3, hardware wallets from different vendors, and storing them in different locations
  20. Sparrow WalletFAQ: the project is licensed under Apache 2, which it describes as open source, and points to the sparrowwallet/sparrow repository
  21. Sparrow Walletsparrowwallet/sparrow repository on GitHub
Free by email

One email. The whole library.

Policy checklist, board paper, recovery drill record, document pack and the rest, in one send. Then one short Thursday lesson for small companies in the UK and the US.

Free. One email with the whole template library, then one short lesson each Thursday. Unsubscribe at any time. See our privacy notice.

Education, not advice.

This is general information and education only. It is not financial, investment, tax, accounting, legal or regulatory advice, and it is not a recommendation to buy, sell or hold bitcoin or any other asset. It does not take account of your circumstances or those of your company. You must obtain your own official professional advice to confirm this information is correct before acting on it.

Rules change. This information is correct to our understanding at the last-reviewed date, but it may be incomplete or out of date, and official sources take precedence. Bitcoin is volatile. A company that buys it could lose some or all of the money it puts in.

Using this site does not create an adviser or client relationship. IoT Financial is not authorised or regulated by the Financial Conduct Authority (FCA) and is not registered with the US Securities and Exchange Commission (SEC) as an investment adviser. Read the full disclaimer.