What is the Lightning Network?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
The Lightning Network is a Layer 2 payment protocol built on Bitcoin that allows two parties to open a payment channel, make thousands of near-instant transactions between themselves off-chain, and then settle the final balance on the Bitcoin blockchain — reducing Bitcoin transaction fees to fractions of a cent for everyday payments.
The Bitcoin payment problem
Bitcoin's base layer processes approximately 7 transactions per second globally. A single coffee purchase would take 10 minutes to confirm and cost more in fees than the coffee during periods of network congestion. Bitcoin was not designed for high-frequency small payments — it was designed as a settlement layer for large, infrequent transfers.
The Lightning Network, proposed in a 2016 whitepaper by Joseph Poon and Thaddeus Dryja, addresses this. The core idea: most transactions do not need to be recorded on the blockchain. If Alice and Bob transact frequently, they only need to record the opening and closing of their relationship on-chain — everything in between can happen instantly, privately, and with no fees, as long as both parties agree on the final balance.
How payment channels work
Alice and Bob each lock some Bitcoin into a shared "funding transaction" on the Bitcoin blockchain — this creates a payment channel. Now they can send value back and forth between each other by exchanging signed messages, each representing a new balance distribution. If Alice sends Bob 0.001 BTC fifty times, only two transactions ever touch the blockchain: the opening and the closing. The channel can stay open indefinitely.
Multi-hop payments — the network
The network aspect: Alice does not need a direct channel with every person she wants to pay. If Alice has a channel with Bob, and Bob has a channel with Carol, Alice can pay Carol by routing through Bob — Bob passes the payment along and earns a tiny routing fee. This web of channels forms the Lightning Network: a payment network where anyone can pay anyone, instantly, for fractions of a cent, without trusting the intermediate routers.
Is it relevant in India?
Yes. Any Bitcoin transaction, including Lightning, falls under India's VDA tax framework. See India tax guide.
🟡 A bit more detail
For when you want to go a little deeper.
Hash Time-Locked Contracts (HTLCs) — the routing mechanism
Multi-hop payments work through HTLCs. When Alice wants to pay Carol via Bob: Carol generates a secret (a random number) and gives Alice only its hash. Alice creates an HTLC with Bob: "I'll pay you 0.001 BTC if you can reveal the secret that hashes to X, or get a refund after T minutes." Bob creates a matching HTLC with Carol: "I'll pay you 0.001 BTC if you reveal the secret." Carol reveals the secret to Bob (claiming Bob's payment), Bob uses that same secret to claim Alice's payment. The secret flows backwards, the money flows forwards. If Carol never reveals the secret, all HTLCs time out and everyone gets refunded — the routing is atomic.
Lightning Network is widely used for Bitcoin micropayments. Strike (a payment app) uses Lightning to enable near-instant Bitcoin payments and cross-border remittances. Twitter/X integrated Lightning tipping in 2021. El Salvador's Bitcoin wallet Chivo uses Lightning for point-of-sale purchases. Lightning is the primary mechanism for Bitcoin streaming payments — paying content creators per minute or per article read, impossible on-chain due to fees. As of 2026, the Lightning Network has over 5,000 BTC capacity locked in channels across tens of thousands of nodes globally.
Channel liquidity and routing challenges
The Lightning Network's practical challenge is liquidity routing. For Alice to pay Carol through Bob, Bob's channel with Carol must have enough outbound capacity. If channels run dry in one direction, payments fail and must be rerouted. Solutions: channel rebalancing (moving funds between channels to restore balance), splicing (adding or removing funds from an open channel without closing it), and liquidity providers (specialised nodes that maintain balanced channels for routing fees).
Key Lightning metrics: total network capacity (BTC locked in channels), number of channels, number of nodes, routing success rate, and average payment size. The routing success rate for large payments is a known challenge — small micropayments route reliably, but larger payments sometimes fail to find sufficient liquidity. Live data: 1ML.com · Lightning Network.
🟣 The full technical picture
For the technically curious.
The Lightning whitepaper: payment channels and HTLC construction
The Poon-Dryja whitepaper (2016) introduces "Revocable Sequence Maturity Contracts" (RSMCs) as the channel update mechanism. Each channel state is represented by a commitment transaction — a partially signed Bitcoin transaction that could be broadcast to close the channel at any time. When Alice and Bob update the channel state, they exchange revocation keys for the previous state — if either party broadcasts an old state, the other can claim all funds using the revocation key. This "penalty" mechanism ensures honest behaviour: cheating on an old state risks losing all channel funds.
Source: Poon, J. & Dryja, T. (2016). The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments. lightning.network/lightning-network-paper.pdf · BOLT specs: github.com/lightning/bolts
BOLTs — the specification standard
Lightning is specified through BOLTs (Basis of Lightning Technology) — a set of interoperability specifications ensuring different Lightning implementations (LND, CLN/c-lightning, Eclair, LDK) can communicate with each other. BOLTs define: the peer protocol (BOLT 1), channel establishment (BOLT 2), onion routing (BOLT 4, using Sphinx mix-format), payment encoding (BOLT 11, the invoice format), and channel announcements (BOLT 7). The Sphinx onion routing used by Lightning provides payment privacy — intermediate routers know only the previous and next hop, not the full payment path or the total amount.
Taproot (Bitcoin's 2021 upgrade) significantly improved Lightning. Pre-Taproot, Lightning funding transactions were identifiable on-chain — a 2-of-2 multisig is visually distinct from regular Bitcoin transactions. Post-Taproot, channel funding uses MuSig2 (a Schnorr signature aggregation scheme) that makes channel funding transactions indistinguishable from single-signature transactions. This "Taproot Channels" upgrade improves Lightning's privacy (channel opens/closes look like normal Bitcoin transactions) and reduces on-chain fees. PTLCs (Point Time-Locked Contracts) — a Taproot-enabled HTLC improvement using scriptless scripts — further improve payment privacy by preventing payment correlation across hops.
Key facts
- Type: Bitcoin Layer 2 payment channel network
- Whitepaper: Poon & Dryja, 2016
- Settlement: Only channel open/close on Bitcoin mainchain
- Privacy: Sphinx onion routing (intermediate hops know only adjacent nodes)
- Implementations: LND (Lightning Labs), CLN (Blockstream), Eclair (ACINQ), LDK (Spiral)
- Network capacity: 5,000+ BTC across tens of thousands of channels (2026)
- Upgrade: Taproot Channels (MuSig2, PTLC-ready)