Lightning Network

Bitcoin for everyday life #

On-chain transactions gain security with further confirmations. A block arrives every ten minutes on average; individual payments can take longer. But for everyday use, that’s not always enough: you don’t want to wait ten minutes at the checkout, and when the network is busy, fees spike. Lightning makes Bitcoin practical for daily life. Payments take seconds, fees are a fraction of on-chain costs. Lightning has also become the common interface: Liquid, Ark, Spark all speak Lightning to the outside world.

How channels work #

A Lightning channel starts with a single on-chain transaction. Two parties, call them Alice and Bob, lock bitcoin into a 2-of-2 multisignature address.

Nobody can spend this money alone. Both signatures are required.

From that moment, Alice and Bob can exchange payments as often as they want without touching the blockchain. They sign new balances. Every signed version would be valid, but only the latest one counts. Cheating doesn’t pay: anyone broadcasting an older balance risks losing their channel balance if the counterparty or its watchtower responds in time.

When closing the channel, two options exist. The cooperative close: both parties agree, one transaction goes on-chain, done. Or the force close: one party closes unilaterally. This is more expensive, takes longer (timelock), and should be the emergency, not the norm.

Routing without a direct channel #

You don’t need a direct channel with everyone.

If Alice pays someone she doesn’t have a direct channel with, the network finds a path through other nodes. The intermediary nodes relay the payment trustlessly, using HTLCs (Hash Time-Locked Contracts). Every payment is atomic: either it arrives in full or not at all. If a payment fails, funds may remain locked until timeouts expire; any required on-chain resolution can incur fees.

The network reality #

Payment success depends on the amount, routing and available liquidity. Multi-Path Payments (MPP), which split a payment into multiple parts, make larger amounts feasible too. For five-figure sums, a direct on-chain transaction is still more reliable and often cheaper.

An important distinction: on-chain fees are based on the transaction’s data size (measured in weight units), not the amount sent. Whether you send 0.01 or 10 bitcoin on-chain costs the same. Paying a higher fee increases the likelihood of confirmation in the next block, but the amount itself is irrelevant. Blocks arrive on average every ten minutes, with considerable variance. Sometimes two minutes, sometimes thirty.

Lightning offers instant finality: the payment confirms and settles in seconds. Fees may include base and proportional components, plus wallet and liquidity costs. Both systems complement each other.

That’s the network. In practice, the wallet determines how much of this you control.

Wallets: which for whom? #

Phoenix is the most mature self-custodial Lightning wallet. ACINQ manages channels in the background. The user sees only balance and payments. ACINQ’s Swaproot update uses Taproot for swap-ins. Phoenix also supports BOLT12, reusable, non-expiring payment requests. Available for iOS and Android. Phoenix is most worthwhile for users who pay with Lightning regularly. The channel opening during onboarding costs an on-chain fee. Occasional Lightning users pay a noticeable premium for this convenience.

Bull Bitcoin Wallet takes a different approach. Instead of managing its own Lightning channels, the app holds smaller amounts on the Liquid network, a Bitcoin sidechain, and swaps into Lightning on demand via Boltz non-custodially. You can send and receive Lightning payments without managing your own Lightning channels. Swap and network fees, and Liquid’s trust model, still matter. Larger amounts are managed on-chain. Open-source, Bitcoin-only, with hardware wallet integration for cold storage.

The trade-off: Liquid is a federated sidechain, not pure Bitcoin. In return, you get instant Lightning compatibility without channel management, better privacy (Liquid encrypts amounts), and simpler onboarding. For most beginners, a good compromise.

Wallet of Satoshi: limited recommendation #

Wallet of Satoshi offers different models depending on the region. Before using it, check whether you are using a custodial service or the Spark-based option and which terms apply. Phoenix and Bull Bitcoin remain our first suggestions.

Lightning Address: email for money #

[email protected] works like an email address, but for money. No QR code, no temporary invoice, no expiration date. A permanent address that anyone can send to at any time.

The LNURL standard powers it, enabling static QR codes and reusable payment requests. For merchants: print a QR code once, it works indefinitely. For content creators and Nostr users, Lightning Addresses are the foundation for zaps, real-time tips.

You can get a Lightning Address through Alby Hub (external) (own node), Stacker News (external), or similar services. Phoenix supports a comparable function natively via BOLT12.

Receiving vs. sending: the liquidity question #

Lightning is asymmetric. Sending is easy: you need balance in a channel. Receiving is more complicated: you need inbound liquidity, capital on the other side of the channel.

Running your own channels means managing your own Lightning liquidity. The first time you receive money over Lightning (e.g., with Phoenix), a channel must be opened. That costs an on-chain mining fee. Phoenix deducts this fee from the first receive and explains it upfront, but many users are still surprised.

You can also use Lightning without your own channels. Wallets like Bull Bitcoin route Lightning payments via Liquid and Boltz swaps, requiring no channel management but involving a different trust model. Which approach fits depends on how often you use Lightning and how much control you want.

More privacy as a side effect #

Lightning was built as a scaling solution, not a privacy tool. But the architecture delivers more privacy than on-chain transactions as a side effect.

Payments travel encrypted through the network via onion routing. Intermediate nodes see only their direct predecessor and successor, never the complete path. On the Bitcoin blockchain, only channel openings and closings are visible. Those are on-chain transactions, not Lightning payments. Individual channel payments are not publicly recorded on the blockchain; participating nodes and service providers can still see payment data.

Taproot can improve privacy for particular operations. Phoenix uses it for swap-ins, for example.

The limitations: the channel network is semi-public. Anyone with a public channel advertises it. Routing nodes see the amounts they forward. Anyone using a custodial service gives up all privacy to the provider. But compared to on-chain, where every transaction is public forever, Lightning is a large step forward.

More on privacy in the Bitcoin context: Privacy & Bitcoin.

For merchants #

Lightning integrates with existing point-of-sale systems. BTCPay Server, the leading open-source Bitcoin payment solution, supports Lightning out of the box. The customer scans a QR code, pays in seconds, the system confirms. Full control when self-hosting, no software licence fee; hosting, network and liquidity costs may apply.

For those who prefer a managed solution: Swiss Bitcoin Pay offers simple onboarding for small businesses, including optional euro conversion, also for Austrian businesses.

More information for businesses: Bitcoin for Businesses.

Limits of Lightning #

Lightning isn’t a replacement for the blockchain. It’s a complement, with structural limits you should know about.

Large amounts remain difficult. Multi-Path Payments have improved the situation, but reliability depends on how well-connected the recipient is. Large exchanges with well-capitalized channels can handle high amounts without issues. Across the broader network, five-figure sums still fail often due to insufficient liquidity on routing paths. For such amounts, a direct on-chain transaction is more reliable and usually cheaper, since on-chain fees don’t depend on the amount.

The wallet must be online. To receive payments and monitor channels, the app needs to be reachable. Wallets like Phoenix can wake the smartphone to accept incoming payments, as long as the device is on and has connectivity. A watchtower can monitor channels while you are away, but it does not receive payments for an offline wallet. In practice, smartphones are usually on, and solutions for the offline problem are in development.

Channel management isn’t a solved problem. Self-custodial wallets like Phoenix abstract away much of the complexity, but the costs for channel openings, liquidity shifts, and force closes still exist. When on-chain fees are high, setting up Lightning for small amounts gets expensive. The onboarding problem, that the first channel requires an on-chain transaction, remains the biggest barrier to broad adoption. Alternatives like Bull Bitcoin sidestep this via Liquid, trading sovereignty for simplicity.

Centralization tendency. The network works most efficiently through large, well-connected routing nodes. That’s good for routing but conflicts with the decentralization ideal. A handful of LSPs (Lightning Service Providers) handle a large share of the traffic.

Lightning is for transactions, not storage. Larger amounts belong in cold storage on-chain. See Security & Storage.

Beyond Lightning: ARK, Spark, and the next generation #

Lightning has proven that fast Bitcoin payments work and has become the common language of the Bitcoin economy. Liquid, Ark, Spark, Fedimint: each subnet speaks its own protocol internally, but they all speak Lightning to each other. That makes Lightning the backbone, even if individual users never touch it.

The well-known limitations (channel management, liquidity lockup, onboarding costs) have spawned a new generation of Layer 2 protocols that make different trade-offs.

ARK does away with payment channels entirely. Multiple users share a common on-chain output via Virtual UTXOs (VTXOs). An ARK operator coordinates transactions. Check the specific security and availability assumptions of the system you use. Receiving works without a prior channel opening, and onboarding is easier than with Lightning, but VTXOs must be renewed periodically, and throughput is more tightly coupled to blockchain capacity. Ark Labs develops the Arkade implementation. Ark and Lightning are complementary and interoperable.

Spark from Lightspark is based on statechains and enables off-chain Bitcoin transfers without channels. A Spark Service Provider co-signs transactions without taking custody. Returning to the blockchain is subject to the protocol’s conditions and security assumptions; it is not equivalent to immediate on-chain availability. Spark is Lightning-compatible. The focus is on payment infrastructure and stablecoin support, which raises questions for Bitcoin-only purists but is relevant for payment adoption.

Both protocols are young, the trust model differs from Lightning, and long-term track records are still being established. But they address real problems that Lightning has grappled with for years: easier onboarding, no channel management, lower entry costs.

FAQ #

Can I send large amounts with Lightning? #

Technically yes, and Multi-Path Payments have improved reliability. But the higher the amount, the higher the Lightning fee, and the more likely routing problems become. For five-figure amounts, a direct on-chain transaction is usually more reliable and cheaper, since on-chain fees don’t depend on the amount.

What happens if my phone breaks? #

Recovery requirements depend on the wallet. Check its documented backup procedure before use. Lightning may require additional channel backups or assistance from a service; a seed phrase alone does not guarantee recovery in every wallet. On-chain wallets may also require a passphrase or wallet configuration.

Is Lightning secure? #

The base protocol is cryptographically robust. The risk lies elsewhere: wallet software, custodial services, and human error. Think of a Lightning wallet like a physical wallet. You carry what you need for the day, not your entire savings. Larger amounts belong in cold storage. Anyone using a self-custodial wallet with proper backups is well set up for daily payments.

What does a Lightning payment cost? #

It depends on the wallet, route and liquidity. Routing fees can include base and proportional components; channel management and swaps can add costs. Check the displayed fees before confirming.