Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 100 of 179

Lightning Network — Deep Dive

How Lightning's payment channels enable instant Bitcoin transactions, the routing challenges that shape the network's topology, and why LN adoption has grown more slowly than early forecasts suggested.

Beginner
8 min readUpdated July 2026Block Clarity Hub Editorial Team

Why Lightning Exists

Bitcoin's base layer processes ~7 transactions per second — too few for high-frequency use like coffee purchases or small remittances. Lightning Network (LN) enables off-chain payments via bilateral payment channels. Two parties open a channel by locking BTC on-chain; they then exchange payments off-chain by updating channel balances; when they're done, they close the channel on-chain. Payments through connected channels can traverse multiple hops. This enables essentially unlimited transaction throughput with instant settlement.

How Payment Channels Work

Alice and Bob open a channel by depositing BTC into a 2-of-2 multisig. They both sign successive versions of the channel state (how much each owns). To pay Bob, Alice signs a new state giving Bob more, Alice less. Bob signs. Neither posts on-chain; the signatures are just held. Either can post the latest state on-chain to close the channel; the network enforces the latest signed state. If someone tries to post an old state, the counterparty can prove it and take all the channel's funds. This design provides economic security without on-chain settlement of every payment.

Multi-Hop Routing

You don't need direct channels with everyone you want to pay. If Alice has a channel with Bob and Bob has a channel with Charlie, Alice can pay Charlie by routing through Bob. Cryptographic techniques (HTLCs — Hash Time-Locked Contracts) ensure the payment atomically completes across all hops or fails atomically. This lets a relatively sparse network handle payments between anyone connected to the graph. Routing efficiency depends on network topology and channel capacities.

  • Payment channels: two parties lock BTC, exchange off-chain payments
  • Multi-hop routing enables payments through connected channels
  • HTLCs ensure atomic payment across hops
  • Enables essentially unlimited throughput with instant settlement

Key Takeaways

  • LN moves payments off-chain via bilateral channels
  • Only channel opens and closes settle on Bitcoin base layer
  • Multi-hop routing enables payments through connected channel graph
  • Instant, low-fee payments with strong cryptographic guarantees

Related Content

Monero Privacy — Deep Dive

How Monero's ring signatures, stealth addresses, and Bulletproof range proofs combine to provide default-on privacy for every transaction, and the regulatory pressures the project faces.

Zcash Architecture

How Zcash uses zk-SNARKs to enable optional shielded transactions, why Sapling was the breakthrough that made shielded pool usage practical, and how Halo2 removed the trusted setup.

Tornado Cash Mechanics and OFAC Context

How Tornado Cash's Merkle tree deposit-and-mix architecture worked, the August 2022 OFAC sanctions, the 2024 Van Loon ruling and the March 2025 delisting, and the broader question of sanctioning immutable smart contracts.

Aztec and Railway — Ethereum Privacy Layers

How Aztec's zkRollup and Railway's stealth-address system approach privacy on Ethereum from different architectural angles, and what shipping ZK-based Ethereum privacy actually looks like.

Liquid Network

How Liquid is a Bitcoin sidechain with faster settlement, confidential transactions, and asset issuance — and where it fits in the Bitcoin scaling ecosystem alongside Lightning.

Validium, Plasma, and State Channels

The scaling designs that lost to rollups — Validium (off-chain data), Plasma (mass exit games), and state channels (bilateral off-chain) — and why understanding them helps make sense of current rollup design.

App-Chains and Rollup-as-a-Service

How Cosmos-style app-chains and modern Rollup-as-a-Service (RaaS) providers (Caldera, Conduit, AltLayer, Gelato) let applications deploy dedicated chains, and the trade-offs vs shared chains.

Cosmos IBC and Interchain Security

How Cosmos IBC enables cross-chain messaging without wrapped assets, how Interchain Security (ICS) lets chains rent security from the Cosmos Hub, and what these primitives mean for Cosmos's app-chain thesis.

References & further reading