Lightning wallet: choose, configure and pay in 2026

The previous article compared mobile apps as a whole. This one digs into what specifically happens on Lightning, Bitcoin's L2 layer. And there is plenty to unpack: Lightning is not a simple option inside an app, it is a system in its own right, with its own actors (LSPs, watchtowers, routing hubs), its own custody×CustodyThe custody of funds. See self-custody and custodial in the dedicated section below.See in the lexicon → trade-offs, its own fee structure and its own limits.

Three decisions shape every serious 2026 Lightning setup. The custody model: do you trust a service with your keys (Wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon → of Satoshi×Satoshi (sat)The smallest unit of bitcoin. 1 BTC = 100 million satoshis. Named after the creator. In 2026, talking in sats becomes common as the price of one BTC rises.See in the lexicon →), a non-custodial×Non-custodialCommon synonym for self-custody in marketing communications.See in the lexicon → Lightning Service Provider (Phoenix), or do you run your own node×NodeComputer that runs the Bitcoin software and takes part in the network by validating blocks and transactions. A « full node » keeps a complete copy of the blockchain.See in the lexicon → (Zeus + LND, Umbrel×UmbrelEquivalent distribution for mini-PCs or Raspberry Pi, with a polished web interface and an app store (BTCPay, mempool.space, Sparrow Server, and so on).See in the lexicon →)? The fee structure: what do you actually pay per transaction, per channel opening, per submarine swap×Submarine swapAtomic exchange between on-chain funds and Lightning funds (and back), trustless, via a provider like Boltz or Lightning Loop. Used to refill or drain channels.See in the lexicon →? The scope of use: Lightning shines for micropayments and speed, but stays constrained by your channels' capacity and their inbound/outbound balance.

This article answers the questions Lightning users ask after six months of real use. How to read a routing fees bill? When a channel closes by itself, where are your funds? What is a Static Channel Backup and why make one? And why, in 2026, does inbound balance remain the hidden topic of every Lightning setup?

Lightning in 90 seconds: the essentials

Lightning is a network of bilateral payment channels anchored on Bitcoin. To pay someone, your wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon → finds a route across one or more intermediate nodes, and each hop transfers a portion of a channel's balance to the next. Transactions are near-instant, and L1 finality is only invoked at opening, closing, or in case of dispute.

Five notions to know to follow the rest.

• Channel. A shared pool between two nodes, created by an L1 transaction (channel opening). The locked sum defines the channel's capacity. Inside, the balance moves freely between both sides without touching the L1 chain.
• Inbound / outbound balance. Within a 1,000,000 sats channel, you may hold 800,000 sats on your side and 200,000 sats on the counterparty's side. You can send up to 800,000 sats (outbound) and receive up to 200,000 sats (inbound). This is the hidden topic of every Lightning setup: without inbound balance, you cannot receive anything.
• HTLC×HTLC (Hashed Time Lock Contract)Contract locked by hash and by time, the building block of Lightning payments: it guarantees that a multi-hop payment is either delivered in full or refunded.See in the lexicon →. Hashed Time-Locked Contract. The cryptographic mechanism that guarantees a multi-hop payment is atomic: it either completes fully, or it is cancelled everywhere. Involves time-locks: if a step stalls, funds are temporarily blocked (hours to days), not lost.
• Watchtower×WatchtowerService that monitors your Lightning node while you are offline and broadcasts a defence transaction if someone tries to close a channel with a fraudulent state.See in the lexicon →. A third-party service that monitors your channel while your wallet is offline, and that can penalise a counterparty trying to cheat by broadcasting an old state. Phoenix and Muun bundle one; a personal node×NodeComputer that runs the Bitcoin software and takes part in the network by validating blocks and transactions. A « full node » keeps a complete copy of the blockchain.See in the lexicon → can use an external one.
• Submarine swap×Submarine swapAtomic exchange between on-chain funds and Lightning funds (and back), trustless, via a provider like Boltz or Lightning Loop. Used to refill or drain channels.See in the lexicon →. An operation that converts L1 sats to Lightning sats, or the reverse, via a minimally-trusted intermediary that matches an on-chain transaction to a Lightning HTLC. Used to rebalance or to move between layers without going through a platform.

For the full conceptual detail (Poon-Dryja, justice transactions, splice), see the Understand Bitcoin guide. The rest of this article assumes these notions are acquired.

The LSP: why everything goes through it in 2026

An LSP×LSP (Lightning Service Provider)Third-party service that helps open Lightning channels and manage liquidity, without holding your funds. Used by mobile wallets like Phoenix.See in the lexicon → (Lightning Service Provider) is a well-connected Lightning node×NodeComputer that runs the Bitcoin software and takes part in the network by validating blocks and transactions. A « full node » keeps a complete copy of the blockchain.See in the lexicon → that acts as an entry point for a user wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon →. Concretely, it opens channels on demand for you, provides the inbound balance you need to receive, and keeps your wallet usable even if you stay offline for several days. Without an LSP, a Lightning mobile wallet would be barely usable for a beginner: you would have to open channels manually, manage liquidity, negotiate inbound balance. The LSP automates all of it.

Four LSP players matter in 2026.

• ACINQ (France). The LSP built into Phoenix. Just-in-time channel model: on your first inbound payment, ACINQ automatically opens a channel of the right size and deducts the fees from the received payment. That is what makes Phoenix feel "zero-conf" in use. The service is paid, but you stay in self-custody×Self-custodyModel in which you hold your own private keys. Your bitcoins depend on no third party. This is Bitcoin's founding promise.See in the lexicon → throughout.
• Voltage (USA). LSP oriented towards hosted nodes and enterprises. Provides managed channels and liquidity on demand. Heavily used by BTCPay merchants who don't want to run their own node.
• Blocktank (Synonym, BitKit team). LSP with a public API×API (Application Programming Interface)Interface that lets one program query another program or service. mempool.space exposes a public API for querying the chain.See in the lexicon →. Buy inbound balance over Lightning and the LSP opens a channel to your node with the requested liquidity. Mature liquidity-as-a-service model in 2026.
• OBW Olympus (United Kingdom). Historical LSP of the OBW wallet (formerly BLW). On-chain or swap-based channel opening, multi-node support.

The zero-conf promise is what drove Lightning mainstream adoption. On channel opening, the L1 anchor theoretically takes 6 confirmations (1 hour) to be fully secure. An LSP like ACINQ offers instead a temporary trust: it considers the channel usable immediately after broadcast, assuming the double-spend risk. For the user, it is instant. The LSP covers this risk through its fees.

Limits to know. First, an LSP is a practical centralisation point. You do not depend on it for your keys (you keep custody×CustodyThe custody of funds. See self-custody and custodial in the dedicated section below.See in the lexicon →), but you depend on it for Lightning connectivity. If ACINQ disappears, you keep your funds, but you will have to force-close your channels and bring the sats back on L1. Second, LSPs are subject to regulatory pressure: an LSP based in a strict jurisdiction can impose KYC×KYC (Know Your Customer)Mandatory identification procedure that regulated platforms apply to their users : ID document, proof of address, and so on.See in the lexicon → on large channel openings. Phoenix partially left the US in 2024 for this reason.

Breaking down Lightning fees

The "Lightning is free" myth is false. Lightning has a cost, simply lower than L1 and structured differently. Five fee types coexist.

• Base fee. A fixed amount in millisats per payment transiting through an intermediate node×NodeComputer that runs the Bitcoin software and takes part in the network by validating blocks and transactions. A « full node » keeps a complete copy of the blockchain.See in the lexicon →. Often 1 sat (1,000 millisats). Independent of the amount transferred.
• Fee rate (ppm, parts per million). A percentage expressed in millionths. 100 ppm = 0.01 %. A 100,000-sat payment via a node at 100 ppm costs 10 sats at that node. The sum of base fee and fee rate across all nodes on the route gives the routing fees.
• Channel opening fees. When an LSP×LSP (Lightning Service Provider)Third-party service that helps open Lightning channels and manage liquidity, without holding your funds. Used by mobile wallets like Phoenix.See in the lexicon → opens a channel for you, it charges L1 mining×MiningProcess of validating blocks through proof of work. Consumes electricity by design : that is what secures the network.See in the lexicon → fees (so dependent on congestion) plus a service margin. Phoenix typically charges 1 % of the amount for just-in-time opening, capped.
• Submarine swap×Submarine swapAtomic exchange between on-chain funds and Lightning funds (and back), trustless, via a provider like Boltz or Lightning Loop. Used to refill or drain channels.See in the lexicon → fees. When your wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon → converts L1 to Lightning (or the reverse) via an intermediary. Typical: 0.1 % to 1 % depending on the service (Boltz, ACINQ, Muun).
• Cooperative closing fees. On amicable channel closing, an L1 transaction is broadcast, paying the current mining fees. Order of magnitude 1 to 5 EUR depending on congestion. Force closing costs more because it broadcasts more transactions.

To set expectations, here is the order of magnitude of a typical 2026 Lightning use on Phoenix.

Three lessons to optimise. First, batch channel openings: Phoenix offers the splice which adds liquidity to an existing channel without opening a new one, much cheaper. Second, aim for short-route payments (1-2 hops) rather than long ones. Third, avoid force-close: it is the most expensive closing, to be reserved for cases where the counterparty is unreachable.

The use cases driving Lightning in 2026

Lightning is no longer experimental. In 2026, six use-case families alone justify a configured Lightning wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon →.

• Prepaid cards and vouchers via Bitrefill. Buy an Amazon, Carrefour, Decathlon, Apple Store voucher, mobile top-up, or a Steam credit by paying with Lightning. De facto standard, available in 180 countries. Lets you spend sats in real EUR/USD without going through an exchange×ExchangeService that lets you buy, sell and swap cryptocurrencies against fiat money. Examples : Kraken, Coinbase, Bitstamp, Bitvavo. Most are custodial.See in the lexicon →.
• Direct commerce via BTCPay. In Switzerland, over 200 merchants accept Lightning via BTCPay Server (watches, restaurants, hotels, services). In France, Germany, Italy, the network is growing but stays more scattered. A good reference map: btcmap.org. A Lightning payment at a merchant takes 1 to 3 seconds, where a bank card takes 10 to 30 seconds.
• Donations and Lightning Address×Lightning AddressEmail-style address (alice@strike.me) that lets you receive Lightning payments without generating an invoice each time.See in the lexicon → (LNURL×LNURLFamily of standards that simplifies Lightning usage: reusable QR codes, withdrawals, authentication. Complemented by readable Lightning Addresses (user@domain).See in the lexicon →-pay). The name@domain.tld format lets you receive Lightning payments as easily as an email. Strike, Wallet of Satoshi×Satoshi (sat)The smallest unit of bitcoin. 1 BTC = 100 million satoshis. Named after the creator. In 2026, talking in sats becomes common as the price of one BTC rises.See in the lexicon →, Voltage, getalby hand out these addresses. Used by content creators, journalists, open-source projects to receive micro-donations without going through PayPal or Patreon.
• Nostr zaps. The decentralised social network Nostr popularised zaps, Lightning micropayments attached to a post. A 100-sat zap (a few cents) is enough to express approval. Mass effect: over 8 million zaps per day in 2025, the main monetisation mechanism for many Nostr creators.
• Gaming and streaming. THNDR Games (mobile games paid in sats), Fountain (podcasts with value-for-value), Wavlake (music with per-stream sats splits) validated Lightning as a micropayment rail. Per-unit amounts are small but they pile up over time.
• Machine-to-machine (M2M) payments and agentic APIs. The L402 standard (HTTP 402 extension) lets AI agents and API×API (Application Programming Interface)Interface that lets one program query another program or service. mempool.space exposes a public API for querying the chain.See in the lexicon → servers pay each other in Lightning sats per request. Growing use case: on-demand API calls, rate-limited access, pay-per-second compute. Still niche in 2026, but structuring for what comes next.

To test in practice without commitment: create a Bitrefill account, buy a 5-EUR voucher paying via Phoenix or Muun, check the transaction goes through within seconds. That is the experience that makes Lightning concrete in five minutes.

Practical limits and Lightning backup

Four Lightning limits to know before using it for anything beyond micro-tests.

• Capped channel capacity. A channel has a fixed size at opening. A 200,000-sat channel (~130 EUR in 2026) does not allow a 250,000-sat payment, even if you have other channels. You must either split the payment (MPP×MPP (Multi-Path Payment)Lightning payment split across several simultaneous paths, recombined on arrival. Allows paying amounts larger than the capacity of a single channel.See in the lexicon →, Multi-Path Payments, handled automatically by good apps), or splice to enlarge the channel.
• Limited inbound balance. To receive sats, you need balance on the counterparty's side. A new wallet×WalletSoftware or device that manages your Bitcoin keys and lets you sign transactions. A wallet does not really « hold » your bitcoins, it holds the keys that prove you own them.See in the lexicon → with no inbound payment has no inbound balance: impossible to receive. ACINQ-style LSPs work around it by opening a channel on your first received payment (just-in-time), but it is billed.
• Routing failures. On multi-hop payments (3+), it sometimes happens that no route suffices. The wallet will retry several times with different routes but may end up failing. More frequent on large amounts (above 1 million sats on a single route).
• Time-locks and force-close. If a channel's counterparty becomes unreachable, you must force-close the channel. It is an L1 transaction that publishes the latest state, and your funds become available after a delay (a number of blocks, so a few hours to several days depending on config). During this delay, the sats are visible on-chain but not spendable.

The Lightning backup differs from the L1 backup. The seed alone is not enough to rebuild the state of a Lightning channel×Lightning channel2-of-2 multisig between two participants that lets them exchange sats off-chain as many times as they like, until they close the channel and publish the final balance on Bitcoin.See in the lexicon →: the most recent commitment transactions are also needed. Three mechanisms coexist.

• Static Channel Backup (SCB×SCB (Static Channel Backup)Static backup of Lightning channels (LND). If the node crashes, it allows requesting the cooperative closing of channels and recovering the funds.See in the lexicon →). LND standard. A small file containing the metadata×MetadataData that describes other data. For a Bitcoin transaction : size, fees, type. For an email : sender, date, subject, without the content itself.See in the lexicon → of all your open channels. In case of node×NodeComputer that runs the Bitcoin software and takes part in the network by validating blocks and transactions. A « full node » keeps a complete copy of the blockchain.See in the lexicon → loss, importing the SCB on a new node lets you ask counterparties to close the channels and recover the L1 balance. You lose funds pending on in-flight HTLCs but recover the stable balance. To back up at each channel opening/closing.
• Channel Force Close×Force closeOne-sided closure of a Lightning channel by one participant. Costs more in fees and locks funds for a challenge period.See in the lexicon → with Phoenix. Phoenix keeps SCBs locally on the phone and backs them up to iCloud/Google Drive in encrypted form. Recovery on a new phone happens via seed + cloud SCB, and Phoenix automatically asks ACINQ to close the channels to repatriate the funds.
• Manual backup for Zeus / personal node. If you run your own node, you must schedule regular channel backups: rsync of the .lnd folder, or SCB export after each opening/closing. Golden rule: test the restore before you need it.

Three best practices to limit headaches. First, never put more than 1,000 EUR on a single channel of a mobile wallet: on force-close, you wait several days to recover. Better to have several mid-size channels than a single large one. Second, periodically (monthly) move the surplus to the hardware via a submarine swap×Submarine swapAtomic exchange between on-chain funds and Lightning funds (and back), trustless, via a provider like Boltz or Lightning Loop. Used to refill or drain channels.See in the lexicon → or cooperative close + L1 send. Third, keep the inbound balance at least 20 % of total capacity, to be able to receive without waiting for a new channel opening.