WalletClauseWallet research workspace
Source-based researchMethod & scope ↗

Bitcoin workflows

Watch-only and multisig: two different wallet tools

Watch-only describes what an installation can see without signing. Multisig describes the approval policy for spending. A wallet can use both, but they solve different problems.

Contents & sources

Watch-only separates observation from authority

A watch-only setup uses public wallet information to display addresses and activity without holding the signing secret. It can help an online computer prepare a request for a separate signer. It cannot normally authorize spending by itself.

Public does not mean harmless to share widely. An extended public key can expose a group of linked addresses and activity. Treat exports and wallet files according to the information they reveal, even when they do not contain private keys.

Multisig changes the spending policy

A multisignature wallet requires an agreed threshold of independent signing keys. A two-of-three arrangement, for example, requires two of the three configured keys. This is an explanation of a policy, not a recommendation that every reader adopt it.

It can reduce dependence on one key, while adding coordination and recovery work. The independence of those keys matters. Three devices in the same bag, backed up in the same place, do not create three independent physical failure domains.

The app is the coordinator

Sparrow documents single-signature and multisignature wallets as well as hardware and watch-only keystores. The coordinator constructs the transaction and collects the required signatures. Individual signers still need to review what they are authorizing.

Document which device corresponds to which key and how the wallet policy is verified. A confusing label or an unrecorded replacement can cause errors later, even if every device remains functional. Keep non-secret identifiers in the plan without putting signing secrets into ordinary notes.

Back up the policy, not just the keys

Recovery may require public configuration that describes the complete wallet: keys, threshold, ordering and script details. Holding enough individual seed backups is not a good reason to discard that configuration. Follow the coordinator’s documented export and recovery process.

Test your ability to reconstruct an unfunded practice wallet before relying on a shared policy. Include the scenario where one signer is unavailable. Know the threshold and avoid “testing” a destructive reset on the only working copy of a necessary record.

Choose complexity for a specific reason

State the problem before introducing multisig: loss of a signer, joint control, a single compromised key or another concrete concern. Then ask what new failure modes the arrangement adds. An arrangement no one can maintain is not resilient just because it has more hardware.

A watch-only view can be useful without multisig, and multisig need not make every computer a signer. Read the Sparrow profile, compare the COLDCARD Q workflow and revisit recovery planning before changing an existing setup.

Sources & scope

Source-based desk research. Checked . Product specifications and documentation can change. No hands-on testing or independent security audit is claimed.

How this research was prepared