Lightning Network

Bitcoin for everyday life #

On-chain transactions are secure and final. Global settlement in about ten minutes, without a middleman. 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.

This article covers how channels work, which wallet suits you, what Lightning can do, and where the next generation picks up.

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 who broadcasts an older balance to the blockchain loses their entire channel balance as a penalty.

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 anything fails along the way, the money returns to the sender.

The network reality #

The Lightning Network keeps evolving. By late 2025, capacity reached an all-time high of over 5,600 BTC (about 490 million euros). The topology has shifted: fewer but better-equipped nodes, around 15,000 active public nodes with nearly 49,000 channels, form an efficient routing network.

Payments up to a few thousand euros work reliably. 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. But fees are percentage-based. The more you send, the more you pay. 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. Since 2025, Phoenix uses Taproot channels, which are cheaper and no longer identifiable as Lightning on the blockchain. Phoenix also supports BOLT12, reusable, non-expiring payment requests. Fees are transparent: 0.4% per payment plus on-chain mining fees for channel management. 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 worrying about channels, liquidity, or onboarding fees. Larger amounts are managed on-chain. Open-source, Bitcoin-only, with Coldcard 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 was long the simplest Lightning wallet. Since January 2026, custodial mode is no longer available in the EU, including Austria, due to DAC8 reporting requirements and MiCA regulation. The remaining “self-custody” mode uses the Spark protocol from Lightspark, a step in the right direction, but the app remains closed-source. Nobody except the operator can audit the code. For maximum simplicity without channel management, it’s an option, but not our first recommendation. Phoenix and Bull Bitcoin offer comparable simplicity with open code.

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 is the most sovereign way to use Lightning. 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. Everything happening within channels stays invisible.

Since Phoenix adopted Taproot channels, even those channel openings and closings are no longer recognizable as such on the blockchain. They look like ordinary Bitcoin transactions.

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, no fees beyond hosting.

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. Users who are often offline need a watchtower, a service that watches in the background. 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 but never has access to the funds. 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. Since late 2025, Arkade, the first mainnet implementation from Ark Labs, has been in public beta. 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. Users retain control and can exit to the blockchain at any time. Spark is Lightning-compatible and has been in mainnet beta since April 2025. 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.

No single protocol will solve everything. Lightning remains the backbone for fast, frequent payments. ARK and Spark make different trade-offs: easier onboarding, less channel management, different trust models.

Detailed articles on ARK and Spark are coming.

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? #

With wallets like Phoenix or Bull Bitcoin, your 12 or 24 words are enough to recover funds. Phoenix stores encrypted channel backups via the ACINQ backend. Users who take the sovereign route with their own node and channels also need a backup of channel states. On-chain bitcoin are always recoverable with the seed.

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? #

Typically between 0.1% and 0.5% of the amount, depending on wallet and setup. Managed wallets like Phoenix have additional minimum fees for channel management. Compared to on-chain fees during high network load, Lightning is cheaper for small and medium amounts. For large sums, the ratio reverses.