Short answer
- Choose custody first, then compare interface and fees.
- Check how the wallet creates inbound liquidity and what happens during an on-chain channel action.
- Keep the initial balance small until you have sent, received, backed up and recovered successfully.
Step 1: choose the control model
A custodial wallet is simplest because the operator manages keys, liquidity and recovery. Managed self-custody keeps user keys while a provider automates much of the channel work. A mobile node or remote-node controller gives more control but exposes more Lightning concepts.
If you cannot explain who can move the funds and what happens when the company disappears, stop before depositing. Do not infer custody from a clean interface or the word “wallet.” Read the project's own explanation and verify whether the recovery material lets you exit without the provider.
Step 2: map the payment pattern
Someone who mostly sends small payments needs reliable outbound routing. Someone who receives tips or sales needs inbound liquidity and may want a reusable Lightning address. A node operator may need channel, peer and fee controls. A podcast listener may care about streaming-payment integrations.
Estimate the largest balance and normal payment size. Lightning is a hot payment system, so do not move a cold-storage balance merely because a wallet can display it. Use an on-chain savings wallet for funds not intended to circulate.
Step 3: inspect the full fee path
Check the cost to add on-chain bitcoin, create or resize a channel, send a Lightning payment, receive when liquidity is insufficient, close a channel and return on-chain. Phoenix, for example, documents routing and on-chain channel costs separately. A wallet can honestly advertise small payment fees while an occasional liquidity operation costs more.
Read the fee shown inside the app before confirming. Mempool conditions change, and Reddit numbers become stale. Also check minimums and what happens when a route fails.
Step 4: test recovery and failure
Start with an amount you can lose. Send and receive, let the app go offline, reopen and sync, export any required channel backup, and learn the force-close path. For a remote-node app such as ZEUS, protect the connection credentials because they may authorize access to substantial node funds.
The comparison page uses this checklist to identify best fits. It is not a guarantee: software, providers and app-store availability can change after review.
Original Reddit discussions reviewed
Open the full threads to inspect dates, replies, disagreements and disclosures. Summaries are our own.
- I did a deep dive of the 7 best Lightning wallets r/lightningnetwork · A current discussion shows that daily spending, self-custody and node management lead to different shortlists; the original post links to the author's own site, so it is treated as one opinion.
- What's your favorite Lightning wallet? r/BitcoinBeginners · Replies expose the friction ladder from custodial apps to managed self-custody and a home node.
- Best Lightning wallet? r/BitcoinBeginners · Users compare Phoenix, Zeus, Breez and custodial options while flagging channel-opening costs and custody tradeoffs.
- Lightning wallets r/BitcoinBeginners · The clearest repeated lesson is to treat Lightning as a spending balance, not a replacement for cold storage.
Official documentation checked
Features and fees can change. Recheck the official page before installing, buying or transferring bitcoin.
- Phoenix wallet ACINQ
- Phoenix splicing and fee model ACINQ
- ZEUS documentation ZEUS
- Blixt features Blixt Wallet
- Blixt backup and channel FAQ Blixt Wallet