Sparrow wallet is a desktop Bitcoin wallet built for PSBT review, multisig, PayNyms, and exact fee control

Sparrow wallet is a self-custody Bitcoin desktop application for people who want to see the details behind every transaction before signing. It manages single-signature and multisig wallets, connects to public servers, Bitcoin Core, or private Electrum servers, and uses PSBT workflows for hardware wallets, airgapped signing, UTXO labeling, coin selection, and fee control.

Its strongest identity is transparency. The app exposes addresses, inputs, outputs, labels, scripts, transaction bytes, and fee choices in a form that remains usable on a normal desktop screen. That makes it useful for a first cold-storage setup, a multisig quorum, a coin-control session, or a transaction review where guessing is unacceptable.

PSBT review before a signature leaves the device

Partially Signed Bitcoin Transactions, or PSBTs, are central to the workflow. A PSBT lets wallet software prepare a transaction while a signing device reviews and signs without needing to hold private keys on the computer. Sparrow wallet uses this standard for both everyday hardware-wallet sends and more advanced multisig coordination.

This matters because the review step becomes concrete. The sender sees which UTXOs fund the payment, which address receives change, which fee rate is being paid, and which signers still need to participate. For airgapped devices, the transaction moves through QR codes or files rather than a direct USB session. For connected devices, the same underlying PSBT model still keeps signing separate from transaction construction.

UTXO labeling turns coin control into a readable map

Bitcoin balances are made from unspent transaction outputs, commonly shortened to UTXOs. Treating them as a single lump hides the history and privacy consequences of spending. Sparrow wallet gives transactions, inputs, and outputs labels, so a user sees the difference between savings received from an exchange, coins from a business payment, and change from an earlier spend.

Coin control then becomes a deliberate selection process. A wallet owner chooses which UTXOs enter a transaction instead of letting the software merge unrelated history without attention. The benefit is practical: the user understands why a transaction has a certain size, why the fee changes, and what information a recipient or chain observer learns from the selected inputs.

Fee control begins before the send button

The fee tools focus on the actual transaction rather than a vague speed label. A larger transaction with many inputs costs more to confirm than a compact one at the same fee rate, so coin selection and fee planning belong together. The interface shows enough structure to connect those details without forcing the user to decode raw Bitcoin data from scratch.

When the mempool is busy, the wallet owner chooses between waiting, increasing the fee rate, or building a smaller transaction from fewer inputs. When block space is quiet, it becomes easier to consolidate UTXOs or move funds to cold storage at a lower cost. Sparrow wallet makes those tradeoffs visible at the moment the transaction is built.

Multisig coordination with hardware signers

Multisig is one of the reasons advanced Bitcoin users choose this kind of desktop wallet. A multisig policy requires more than one key to authorize spending, such as a two-of-three arrangement using separate hardware wallets. The setup protects against a single lost or compromised signer while still allowing recovery through the remaining quorum.

The software supports common script types and works with many hardware wallets through USB and airgapped modes. In a multisig send, the transaction is constructed once, then each signer contributes its signature. Sparrow wallet displays the signing progress and the transaction details, which reduces confusion when several devices, backups, or people are involved.

PayNyms and BIP47 for reusable contacts

PayNyms bring a contact-style layer to Bitcoin receiving without turning every payment into a reused public address. They are based on BIP47 payment codes, which let wallets derive fresh addresses for transactions between parties. This gives users a recognizable contact identity while preserving the habit of avoiding address reuse.

The wallet supports direct PayNym payments and collaborative PayNym workflows. That feature fits people who send to the same counterparty more than once, want a cleaner contact experience, or use privacy-focused transaction patterns. It is still Bitcoin on-chain activity, so fees and confirmation times follow the network rather than an account system inside the app.

Server choices shape privacy and verification

A desktop wallet needs blockchain data to show balances and prepare transactions. The connection choice changes what the wallet reveals and how independently it verifies information. Public servers are quick to start with. Bitcoin Core gives the user a local full-node path. Private Electrum servers add a wallet-indexing layer that pairs well with a full node.

Sparrow wallet also includes built-in Tor support, which helps separate network activity from an ordinary internet connection. Testnet, regtest, and signet support give developers and careful operators a place to practice receiving, sending, and signing without using mainnet coins. Those environments are especially useful before building a large multisig or teaching someone the PSBT flow.

The transaction editor doubles as a blockchain explorer

The built-in transaction editor is the feature that separates the app from lighter wallets. It lets a user inspect and edit transaction fields, then examine the serialized bytes before broadcast. That level of detail helps with fee analysis, script review, multisig debugging, and understanding exactly what a transaction commits to.

Because the editor also works as a blockchain explorer, the same environment used for wallet activity becomes a learning and inspection tool. A user studies inputs, outputs, change, locktime, and raw structure without switching between a wallet and a separate website. Sparrow wallet is especially valuable when the question is not only whether a transaction sends, but why it looks the way it does.

Getting started with a desktop-first Bitcoin setup

The setup path begins with downloading the application for the user's operating system, creating or importing a wallet, and choosing a connection method. A new user who owns a hardware wallet pairs the device, confirms wallet policy details, and tests receive addresses before moving serious funds. Someone building multisig records the policy, signers, derivation paths, and backup material with extra care.

A sensible first session includes a small receive, a labeled transaction, and a low-value send. That sequence teaches address verification, UTXO creation, hardware signing, change output review, and fee selection in one controlled loop. Once those pieces are familiar, larger workflows such as cold storage deposits, collaborative signing, and PayNym contacts feel less abstract.

Where Electrum, Bitcoin Core, and mobile wallets fit beside it

Electrum remains a respected option for experienced Bitcoin users who want a lightweight wallet with scripting depth and plugin history. Bitcoin Core provides full-node validation and a native wallet, though its wallet interface has a different emphasis from a PSBT-centered desktop workflow. Mobile wallets serve quick spending and scanning well, especially when convenience matters more than detailed review.

Importantly, Sparrow wallet occupies the desktop review lane: hardware-wallet coordination, transaction construction, UTXO management, labels, and fee control in one place. It is the better fit when the user wants a workstation for Bitcoin operations rather than a pocket spending app. The Apache 2 licensed project also gives technically minded users a familiar open-source software model to inspect and build around.