sparrow-wallet.app Independent guide Buy bitcoin to self-custody

Scope · reviewed 2026-08-10

Bitcoin, on-chain, and nothing else

That is the whole answer. No Ethereum, no stablecoins, no tokens, no NFTs, no Lightning balances, no browser extension, no WalletConnect, and no staking of any kind. If you came here hoping one of those was hiding in a settings menu, it is not, and the rest of this page explains what Sparrow does instead — and what to use for the things it refuses.

Compare current bitcoin prices

  • Bitcoin only
  • On-chain only
  • Desktop only
  • No tokens
  • No Lightning
  • No yield

Unofficial

Asked about, versus reality

These are the capabilities people search for alongside Sparrow's name. Almost all of them are answered with a flat no, which is exactly why the question keeps being asked.

Compiled from the official Sparrow feature documentation and release notes; the right column is this site's recommendation.
CapabilityIn SparrowWhat actually works instead
Bitcoin, on-chainYesThe entire scope of the wallet
Lightning Network paymentsNoRun Lightning node software; keep the on-chain reserve in Sparrow
Ethereum and EVM chainsNoUse a separate wallet for that ecosystem
Stablecoins (USDT, USDC)NoNot bitcoin; nothing in Sparrow can hold them
Tokens, memecoins, NFTsNoNo token list, no approvals, no gallery
Ordinals and inscriptionsNot a featureCoin control helps you avoid spending an odd UTXO by accident
Browser extensionNoDeliberately a desktop application, not browser based
WalletConnect, dApp connectorNoNo web3 surface exists to connect
Staking, yield, "Babylon staking"NoSelf-custody wallets do not pay yield
Built-in swaps or exchangeNoBuying happens elsewhere; Sparrow only holds keys
CoinJoin or mixingNo longerWhirlpool was removed — see the privacy page
Official mobile appNoDesktop only; store listings using the name are fakes

Source: sparrowwallet.com — features

The other side of the ledger

What it does support, properly

Narrow scope is not the same as thin functionality. Within Bitcoin, Sparrow covers more ground than most wallets attempt, and it does so with formats other software can read.

Address and script types

Legacy P2PKH
The original address format, still needed for old backups and old counterparties.
P2SH-wrapped SegWit
The compatibility format for services that never updated their address validation.
Native SegWit P2WPKH
The sensible default for most wallets: cheaper inputs, wide support.
Taproot P2TR
The newest output type, with cheaper key-path spends and better script privacy.

Wallet structures and key material

Single signature
One key, one signature. The normal case, from BIP39 seed words or a hardware signer.
Multisig
Real quorums such as 2-of-3, exported as output descriptors — a text description of the wallet's keys and rules that another compatible wallet can rebuild from. Multisig walkthrough.
Watch-only xpub
An extended public key that derives your addresses but cannot sign, so you can monitor a cold wallet from an online machine with no signing capability present.
PSBT throughout
Partially Signed Bitcoin Transactions, supported from the ground up — the standard file that lets an unsigned transaction travel to an offline signer and back.

Test networks

Testnet, signet and regtest are all supported, which means you can practise a full multisig or airgapped workflow with worthless coins before you touch real ones.

Signing paths

Software keystore, USB hardware wallets, and airgapped signing over SD card or QR fountain codes using the UR standard. Device support table.

Portability

Output descriptors, BIP39 seeds and Electrum wallet import and export, so nothing you create is trapped inside this one application.

Lightning: why an on-chain wallet cannot simply add it

This is the most common question about Sparrow, and it deserves a real answer rather than a one-word refusal. Lightning is not a feature that a Bitcoin wallet can switch on. It is a different system that settles on Bitcoin, and running it means running infrastructure.

What Lightning actually is

A Lightning payment does not touch the blockchain. Two parties lock funds into a two-of-two channel with one on-chain transaction, and after that they update the balance between themselves privately, as many times as they like, by exchanging signed states. Payments route across chains of these channels, so you can pay someone you have no direct channel with. Only opening and closing the channel are on-chain events. That is what makes it fast and cheap, and it is also what makes it structurally different from everything Sparrow does.

Why "just add Lightning" is not a small ask

Four things stand in the way, and none of them are about effort.

  • Channels are not addresses. Money in a channel is not a UTXO you can spend at will; it is a jointly held position with a counterparty who has to cooperate, or be forced on-chain through a timelocked closing procedure.
  • Liquidity has to be managed. You can only receive what your channel partners can send toward you. Inbound liquidity is an ongoing operational concern, often a paid one, and it has no equivalent in on-chain wallets.
  • It wants to be always on. A node that is offline cannot route, cannot reliably receive, and cannot watch the chain for a counterparty who closes a channel using an old state. A desktop wallet you open twice a week is the wrong shape for that job.
  • Backups are nothing like a seed phrase. This is the part that catches people. On-chain, twelve words written on paper recover everything forever. In Lightning, your seed is not sufficient: channel state changes with every payment, and restoring an outdated backup can cost you the channel balance. It requires continuous state backup with completely different semantics.

Bolting that onto a wallet whose entire value proposition is deliberate, auditable on-chain construction would compromise both halves. The project's answer is to do one layer properly.

The realistic 2026 setup

In practice people run both, with a clear division of labour. Lightning node software — self-hosted on a small always-on machine, or a mobile Lightning wallet if you accept the trade-offs — holds a modest spending balance for instant, low-fee payments. Sparrow holds the on-chain reserve underneath it: the savings, the cold storage, the multisig quorum, the coins you are not spending this month.

The two touch at exactly two points. When you fund a channel, you are making an ordinary on-chain payment to a two-of-two output, and Sparrow is a good place to make it from because you can choose which coins to use and see the fee before you sign. When a channel closes, the funds land back on-chain at an address you control, and Sparrow is a good place for them to land. Think of it as a current account and a vault, not as a wallet with a missing tab.

Abstract representation of a bitcoin wallet holding keys rather than coins

One layer each

A Lightning node for spending, Sparrow for the reserve. Closing a channel to an address in a wallet you control is the normal end of a channel's life — which means your on-chain backups still matter more than anything else you do.

"Babylon staking" and bitcoin yield

This search term brings people to wallet pages regularly, so here is the direct answer: Sparrow has no staking feature, no yield product, and no integration with any protocol that offers one. There is no menu to look for.

The reason is not laziness. Bitcoin has no native staking mechanism — there is no consensus role your coins can perform in exchange for issuance. Every product that offers a return on bitcoin therefore has to manufacture one, and it does so in one of three ways. It takes custody, in which case you have lent your coins to a company and you are exposed to its solvency. It locks them into a contract or bridge, in which case you are exposed to that code and whoever can upgrade it. Or it imposes slashing conditions, in which case a technical fault, a downtime event or a misbehaving operator can destroy part of your principal.

All three require you to give up unilateral control of your keys. That is the precise thing a self-custody wallet exists to prevent, which is why no honest self-custody wallet will ever ship a yield button. If a return is being offered, someone is taking a risk, and if you cannot name whose balance sheet absorbs a loss, the answer is yours.

Ordinals and inscriptions

Sparrow is not an ordinals wallet. It will not render an inscription, catalogue a collection, or help you buy or sell one. Presenting it as inscription tooling would be misleading.

Its actual relevance to the subject is protective and worth understanding. Because Sparrow shows you your individual UTXOs and lets you decide which ones a transaction spends, you can leave an unusual coin alone. Wallets that select inputs automatically have no idea that one particular UTXO means something to you, and will happily consume it as part of an ordinary payment or push it into a change output. Coin control is how you avoid that, and it is the same mechanism described on the privacy page.

If your goal is actively trading inscriptions, use software built for it and keep it away from your savings. If your goal is not losing something by accident, label the UTXO and never select it.

Why Bitcoin-only is a security decision

Every additional chain a wallet supports arrives with its own address formats, its own signing rules, its own node dependency and its own libraries. The attack surface grows faster than the feature list, and the code that handles your keys grows with it.

Sparrow's refusals remove whole categories of failure rather than individual bugs. There is no token-approval mechanism, so there is nothing to trick you into approving and no allowance for a drainer to exploit later. There is no injected web3 provider, because there is no browser extension and no dApp connector. There is no RPC connection to a chain whose rules a foundation can change next quarter. And the dependency list stays short enough that a supply-chain compromise has fewer doors to come through.

The project is explicit that it is not browser based, describing browser technology as a large attack surface and shipping a tab-based desktop application instead. Read that as a statement of priorities: fewer capabilities, more of them verifiable. The feature walkthrough shows where that budget was spent instead.

Source: sparrowwallet.com — FAQ

Direct answers to the questions people type

Does Sparrow Wallet support the Lightning Network?

No. Sparrow is an on-chain Bitcoin wallet: it builds, signs and broadcasts transactions that settle on the base layer. It cannot open a channel, hold a Lightning balance or pay an invoice. Lightning requires separate node software. The two work well side by side, with Sparrow holding the on-chain funds and the Lightning node holding a smaller spending balance.

Does Sparrow Wallet support Ethereum, USDT or other coins?

No, and it never will — this is a design decision rather than a missing feature. Sparrow understands Bitcoin script, Bitcoin addresses and Bitcoin transactions only. There is no token list, no contract interaction and no multi-chain layer. If you need one application for several chains, Sparrow is the wrong tool and you should not try to force it.

Is there a Sparrow Wallet Chrome extension or WalletConnect support?

No to both. The project describes itself as a tab-based desktop wallet and treats browser technology as a large attack surface, so there is no extension, no injected provider and no WalletConnect session. Anything advertising itself as a Sparrow browser extension should be treated as hostile. See the security page.

Can I stake bitcoin or earn yield in Sparrow?

No. Sparrow has no staking feature of any kind. Bitcoin has no native staking, so every product offering yield on bitcoin does it by taking control of your coins, by relying on a contract you must trust, or by imposing slashing conditions. A self-custody wallet whose whole purpose is that you hold the keys cannot participate in that, and this site does not encourage it.

Does Sparrow Wallet support ordinals or inscriptions?

Not as a feature. Sparrow will not display an inscription or help you trade one. Its relevance is the opposite: because you can inspect and select individual UTXOs, you can keep an unusual coin from being swept into an ordinary payment as change. If trading inscriptions is your goal, you need dedicated software, not this wallet.

What does Sparrow support, then?

Single-signature and multisig wallets on the common script types — legacy P2PKH, P2SH-wrapped SegWit, native SegWit P2WPKH and Taproot P2TR — with full PSBT support, watch-only xpub keystores, output descriptors, hardware signers over USB and airgapped, and mainnet plus testnet, signet and regtest. Version 2.5.3 is the current release line.

Is Bitcoin-only a limitation or a security feature?

Both, honestly, but the security side is underrated. A wallet that supports one chain has fewer dependencies, no token-approval mechanism to be tricked into, no RPC connection to a network whose rules someone else changes, and a codebase small enough that a careful reader can follow it. Most catastrophic wallet losses in other ecosystems involve exactly the machinery Sparrow does not have.

Who is genuinely worse off, and what they should use

Scope decisions have real costs. Pretending otherwise would be as dishonest as pretending the features exist.

You want one app for several chains

You need a multi-chain wallet, and you will accept the larger attack surface that comes with one. Keep the bitcoin you are not actively using out of it.

You make frequent small payments

You need a Lightning wallet or your own Lightning node. On-chain fees make small payments uneconomic no matter which wallet builds them.

You transact mostly from a phone

You need a reputable mobile Bitcoin wallet, because there is no official Sparrow mobile build at all. Why that matters.

You interact with web applications

You need a browser-extension wallet, and you should treat it as a hot wallet with a small balance rather than storage.

The verdict on scope

Sparrow is not a crypto wallet in the general sense. It is a Bitcoin instrument: single-sig and multisig, four script types, full PSBT support, airgapped signing, watch-only monitoring and output descriptors, all in release line 2.5.3. If your holdings are bitcoin and your priority is keeping them, the narrow scope is the reason to choose it.

If your portfolio spans several chains, use Sparrow for the bitcoin portion and something else for the rest. Do not try to make one application do both — that instinct is how people end up with their long-term savings sitting behind a browser extension. Start with a correctly configured wallet, then your own node.

One asset, held properly

Sparrow only ever holds bitcoin, which makes the decision simple: acquire it on a platform that handles the regulated part, then withdraw to keys nobody else can touch.

See current bitcoin prices