What is the Bitcoin Lightning Network, and how does it work?

The Scalability Problem of the Bitcoin Base Layer

The base layer of the Bitcoin blockchain prioritizes decentralization and security over transaction speed, which limits its ability to process high volumes of payments.

When the Bitcoin network launched in 2009, it introduced a method for peer-to-peer electronic cash that operates without a central authority [Source]. To achieve this, the network relies on thousands of independent computers, known as nodes, located around the world, each verifying and storing a copy of every transaction. To keep the blockchain manageable for everyday users running standard home computers, the network imposes a block size limit and a ten-minute target for block generation.

Because of these design constraints, the Bitcoin base layer can only process roughly seven transactions per second [Source]. During periods of high demand, users compete for limited block space by offering higher fees. This works well for settling large, high-value transfers: if an institution is moving millions of dollars in value, waiting an hour for secure settlement and paying a moderate fee is efficient compared to a traditional bank wire.

This architecture is less practical for microtransactions. Paying a five-dollar on-chain fee and waiting ten to sixty minutes to buy a small cup of coffee is not a workable model for daily commerce. Matching the throughput of global payment processors, which routinely handle tens of thousands of transactions per second, would require blocks so large that only well-resourced data centers could afford to run nodes [Source]. That would undermine the decentralization the network is built on.

Instead of compromising the base layer, developers turned to secondary protocols. This gave rise to Layer 2 networks, which build on the security of the primary blockchain while speeding up transactions.

What Is the Bitcoin Lightning Network?

The Bitcoin Lightning Network is a decentralized system of smart contracts that lets users route instant, high-volume payments off the main blockchain.

First proposed in a 2016 whitepaper by developers Joseph Poon and Thaddeus Dryja, the Lightning Network was designed to address Bitcoin's scalability limitations [Source]. The protocol works as an overlay peer-to-peer network. Instead of broadcasting every transaction to the global Bitcoin network, participants open private, two-party payment channels directly between themselves.

Within these channels, users can transact many times, updating their respective balances instantly. The main Bitcoin blockchain is used only at the start and end of the relationship, once to open the channel and once to close it [Source]. The blockchain steps in only to enforce the final balances or resolve disputes if a participant tries to act maliciously [Source].

For a Canadian user, using the Lightning Network can feel similar to tapping a debit card. Transactions typically settle in milliseconds, and fees are often measured in fractions of a cent, denoted in satoshis. This is why the Lightning Network is widely used for Bitcoin micro-payments, remittances, and digital tipping.

Layer 1 vs. Layer 2 at a glance:

• Transaction speed: Base layer, roughly 10 minutes to hours. Lightning Network, milliseconds.
• Throughput capacity: Base layer, about 7 transactions per second. Lightning Network, theoretically much higher.
• Transaction fees: Base layer, variable and often several dollars during congestion. Lightning Network, typically fractions of a cent.
• Privacy: Base layer, a public, pseudonymous ledger. Lightning Network, onion-routed for higher privacy.
• Primary use case: Base layer, large settlements and cold storage. Lightning Network, microtransactions and daily purchases.

How Do Lightning Network Payment Channels Work?

Lightning Network payment channels work by locking funds into a multi-signature address on the blockchain, then updating the balance off-chain through a series of cryptographic agreements.

The process begins with a funding transaction. Picture two parties, a customer in Calgary and a local merchant, agreeing to open a channel. The customer deposits Bitcoin into a 2-of-2 multisignature address on the main Bitcoin blockchain [Source]. This address is a smart contract that requires digital signatures from both parties to move funds.

Once the funding transaction confirms, the channel is open. Its total capacity is set by the initial deposit. If the customer deposits 0.05 BTC and the merchant deposits nothing, the channel has a capacity of 0.05 BTC, and at that moment the entire balance sits on the customer's side.

As the customer makes purchases, the two parties exchange commitment transactions off-chain [Source]. A commitment transaction is a valid Bitcoin transaction reflecting the newly agreed distribution of funds. For example, after a purchase, the new state might allocate 0.04 BTC to the customer and 0.01 BTC to the merchant. Both parties sign this new state and exchange cryptographic secrets that invalidate the previous one. Because these commitment transactions are not broadcast to the network unless the channel is closing, they carry no on-chain fee and settle instantly.

Managing Channel Balances and Liquidity

Liquidity management governs the flow of funds within the Lightning Network, requiring users to balance outbound capacity for sending payments against inbound capacity for receiving them.

When a user opens and funds a channel, all of the capacity sits on their side [Source]. That gives them outbound liquidity to send payments, but since the counterparty's side is empty, they have no inbound liquidity and cannot receive a payment until they spend some outbound funds or another user opens a channel toward them [Source].

This historically made it harder for merchants and casual users to receive funds. To address it, the ecosystem developed the Lightning Service Provider (LSP), a specialized node offering infrastructure services such as leasing inbound liquidity for a small fee [Source]. Modern mobile wallets integrate with LSPs behind the scenes: when a new user tries to receive a payment without existing inbound liquidity, the LSP can open a new channel on the fly, deduct a small setup fee, and deliver the funds.

Nodes also typically maintain a channel reserve balance. To keep both parties financially deterred from attempting fraud, the protocol generally requires each participant to keep a small percentage of the total channel capacity locked on their side [Source]. This discourages a user from fully draining their side of the channel and then having nothing to lose by broadcasting an old, fraudulent state.

Routing Payments: HTLCs and Onion Routing

The Lightning Network routes payments across multiple intermediaries using Hash Time-Locked Contracts and onion routing, so funds are delivered securely and privately without requiring a direct channel to every recipient.

Opening a direct payment channel with every merchant or individual would be capital intensive and inefficient. Instead, the Lightning Network operates as an interconnected web of channels. If a user wants to pay a recipient but only has a channel open with an intermediary, the network can route the payment through that intermediary.

To prevent the intermediary from simply keeping the funds, the protocol uses Hash Time-Locked Contracts, or HTLCs, a cryptographic conditional payment built into the channel's commitment transaction [Source]. An HTLC enforces two conditions:

• The hashlock: the payment can only be claimed if the receiving node produces a secret, called the preimage, that hashes to a specific value in the contract.
• The timelock: if the preimage is not provided within a set timeframe, measured in blockchain blocks, the contract expires and funds revert to the sender [Source].

When a sender initiates a payment, the recipient generates a secret preimage and sends its cryptographic hash to the sender. The sender creates an HTLC with the first intermediary, locking funds so the intermediary can only claim them by revealing the secret. The intermediary creates a corresponding HTLC with the next node in the route, and so on until the recipient claims the funds by revealing the secret. Each intermediary then uses that secret to claim their own funds from the previous node [Source]. This chain cascades backward across the route in milliseconds, so intermediaries either forward the payment successfully or the transaction fails safely.

To protect privacy during routing, the Lightning Network uses a data format called the Sphinx protocol, an onion-routing mechanism conceptually similar to Tor [Source]. When a payment routes across multiple nodes, the instructions are wrapped in layers of encryption, and each node can only unwrap the layer meant for it.

An intermediate node therefore only knows the identity of the immediate predecessor and successor in the route [Source]. It cannot see the route's full length, the original sender, or the final destination. This compartmentalization is central to preserving financial privacy and limiting the ability of large routing hubs to surveil traffic or run balance discovery attacks against competing nodes [Source].

The Role of Watchtowers and Force Closures

The security of off-chain transactions relies on penalty mechanisms, watchtower monitoring, and the ability to force close a channel if a counterparty behaves maliciously or goes offline.

Because Lightning transactions happen off the main blockchain, there is a theoretical risk that a party could try to cheat by broadcasting an older, more favourable commitment transaction to overwrite the current state.

To discourage this, the protocol issues a unique revocation key for every updated state [Source]. When participants agree to a new balance, they exchange the revocation key for the previous one. If a party broadcasts a revoked commitment transaction, they do not get the funds immediately: the protocol enforces a timelock delay on the cheating party's funds [Source]. During that delay, the honest counterparty can use the revocation key to generate a penalty transaction and claim the funds in the channel [Source]. This penalty design is meant to make cheating unprofitable.

When users are finished transacting, they can perform a mutual close: both parties sign a final closing transaction and broadcast it, paying a standard on-chain fee. If one party goes offline or becomes unresponsive, the other can initiate a force close by unilaterally broadcasting the latest valid commitment transaction [Source].

The main vulnerability occurs if an honest user's node is offline when a counterparty tries to broadcast an old state. If the honest user does not come online before the timelock expires, they cannot publish the penalty transaction. To automate this protection, the ecosystem relies on watchtowers, third-party nodes that monitor the blockchain for breaches [Source]. If a watchtower detects an old commitment transaction being published while the honest user is offline, it can broadcast the penalty transaction on the user's behalf [Source].

The Standards: Understanding BOLT Specifications

The Basis of Lightning Technology (BOLT) specifications are the rulebook that keeps different Lightning Network software implementations compatible with one another.

Because the Lightning Network is an open-source protocol, various teams have built their own node software. Well-known examples include the Lightning Network Daemon from Lightning Labs, Core Lightning from Blockstream, and Eclair from ACINQ [Source].

For the network to function as a single liquidity pool, a merchant running Eclair needs to be able to route a payment through an intermediary running Core Lightning and settle with a customer using the Lightning Network Daemon. Without a shared standard, the network would fragment into incompatible silos.

The BOLT specifications guarantee this interoperability [Source]. Maintained on GitHub by the open-source community, BOLTs work similarly to Bitcoin Improvement Proposals but are specific to the Layer 2 network [Source]. A feature is only adopted into the standard once multiple independent implementations demonstrate working interoperability [Source].

The protocol stack is divided into specific documents:

• BOLT 1 (Base Protocol): defines peer-to-peer messaging, transport encryption, and feature negotiation [Source].
• BOLT 2 (Peer Protocol): covers the lifecycle of a payment channel, including opening, updating HTLCs, and closing it [Source].
• BOLT 3 (Transaction Formats): specifies the Bitcoin scripting used for commitment, funding, and penalty transactions [Source].
• BOLT 4 (Onion Routing): details the Sphinx protocol that keeps payment routing private across hops [Source].
• BOLT 7 (P2P Node Discovery): explains the gossip protocol nodes use to broadcast their existence, channel capacities, and fees [Source].

Modern Upgrades: BOLT 12, Splicing, and Taproot Assets

Recent advancements, including reusable BOLT 12 offers, dynamic channel splicing, and the Taproot Assets protocol, have improved network efficiency and enabled new use cases.

Historically, requesting a payment meant generating a BOLT 11 invoice. BOLT 11 invoices can only be paid once, carry expiration timers, and must be generated dynamically by a live server for every transaction [Source]. That made recurring subscription payments, static donation QR codes, or a payment code printed on a storefront difficult to support safely.

BOLT 12 offers address this by introducing reusable payment requests [Source]. An offer is a static string that lets a payer's wallet communicate directly with the receiver's node over the Lightning Network. The wallet requests an invoice at the moment of payment, and the receiver's node generates it instantly without an external web server. This lets a merchant post a single, permanent QR code. BOLT 12 also introduces route blinding, which gives receivers more privacy by shielding their node's public key from the payer [Source].

BOLT 11 vs. BOLT 12 at a glance:

• Reusability: BOLT 11 is single-use only. BOLT 12 offers are reusable for multiple payments.
• Expiration: BOLT 11 invoices are strictly time-bound. BOLT 12 offers can be posted with no expiry.
• Privacy: BOLT 11 exposes the receiver's node ID. BOLT 12 supports route blinding for receiver anonymity.
• Payment types: BOLT 11 supports one-off transactions only. BOLT 12 supports recurring subscriptions and donations.
• Network reliance: BOLT 11 requires an external server to generate invoices. BOLT 12 uses native node-to-node communication via onion messages.

Channel splicing is another step forward in capital efficiency. Previously, increasing a channel's capacity meant closing it, paying an on-chain fee, and opening a new, larger channel, paying a second fee. Splicing lets users resize a channel by adding or removing funds through a single on-chain transaction [Source], while the channel stays operational for off-chain payments during the resizing transaction's confirmation. Several major implementations now support splicing [Source].

Finally, the Taproot Assets protocol extends the Lightning Network beyond its native asset. It lets developers issue distinct digital assets, such as fiat-pegged stablecoins, directly on the Bitcoin blockchain, which can then be deposited into Lightning channels and routed globally [Source]. Intermediary routing nodes continue forwarding standard Bitcoin, unaware of the alternative assets, while the protocol handles conversion at the network's edges [Source].

The State of the Lightning Network in 2026

The Lightning Network has matured into established financial infrastructure, marked by concentrated routing hubs, rising transaction volumes, and a shift toward private channels.

Tracking the exact size of the network has become harder as the technology matures. According to mempool.space, public Lightning Network capacity has consolidated after peaking at roughly 5,600 BTC in late 2025, leveling out between 4,100 and 4,898 BTC across roughly 16,000 to 17,400 active nodes and 41,000 channels [Source].

This contraction in public metrics does not mean adoption is shrinking. Rather, it reflects a shift in how major entities interact with the protocol: exchanges have integrated Lightning infrastructure and moved large daily payment volumes into private channels that do not appear in public capacity metrics [Source]. Publicly measurable transaction throughput crossed well over a billion dollars monthly by late 2025 [Source].

The network topology is also fairly centralized. A relatively small group of well-capitalized routing hubs, often operated by exchanges and LSPs, controls a large share of routing liquidity [Source]. This hub-and-spoke model routes payments efficiently but moves the network away from a fully distributed mesh. Node uptime, liquidity balancing, and on-chain fees during congestion remain a real hurdle for hobbyist node operators, which continues to push volume toward professional LSPs [Source].

Centralized vs. Self-Custody Lightning Wallets

Choosing how to interact with the Lightning Network means weighing the convenience of custodial platforms against the self-sovereignty of non-custodial software.

A crypto wallet lets users store and interact with digital assets. For the Lightning Network specifically, users need to decide who manages channel liquidity, node uptime, and private key security.

Self-custody Lightning wallets, such as mobile apps like Phoenix or Breez, give users control over their own private keys, without relying on a third-party custodian. Modern self-custodial wallets use LSPs to automatically open channels, splice, and manage inbound liquidity, which makes the experience more approachable for beginners. Users remain responsible for safeguarding their recovery seed phrase; if it is lost, the funds are unrecoverable, and self-custody users can be exposed to on-chain fees when their wallet needs to open or splice a channel.

Centralized custodial platforms remove much of this complexity. With centralized crypto custody, a regulated corporate entity manages the infrastructure, routing nodes, channel balancing, and cryptographic security. Users generally don't need to manage inbound liquidity, on-chain fees for channel management, watchtowers, or forced channel closures themselves. The trade-off is the counterparty risk that comes with trusting a third party to hold assets. Netcoins, for example, uses a hybrid custody model with Fireblocks for hot wallet management and BitGo for multi-signature cold storage [Source].

Self-custody wallets tend to suit users who prioritize decentralization and are comfortable managing their own keys. Custodial platforms tend to suit beginners who want a more guided entry into cryptocurrency.

How Canadians Can Start Using the Lightning Network

Canadians can access the Lightning Network by moving from traditional banking to a regulated cryptocurrency platform to acquire the underlying Bitcoin.

Because the Lightning Network requires actual Bitcoin to open a channel, users first need to acquire the asset on the base layer. One option is to learn how to buy Bitcoin in Canada using a regulated domestic platform.

The general steps for onboarding from fiat to the Lightning Network:

1. Fund an account: register with a secure Canadian crypto exchange like Netcoins and fund it by linking a bank account and sending an Interac e-Transfer, which typically settles in under thirty minutes with no deposit fee [Source].
2. Buy Bitcoin: once the Canadian dollars are credited, place a standard buy order on the spot market.
3. Choose a Lightning wallet: download a mobile Lightning wallet, such as Phoenix or Wallet of Satoshi [Source].
4. Transfer funds on the base layer: withdraw the purchased Bitcoin to the wallet address the app provides. This step happens on the base layer and takes standard confirmation time.
5. Transact on Lightning: once funds are in the Lightning-enabled wallet, scan merchant QR codes, use BOLT 12 offers, or send remittances with low fees.

People Also Ask About the Bitcoin Lightning Network

How much does a Lightning Network transaction cost?Transactions on the Lightning Network generally cost fractions of a cent, which makes it well suited to micro-payments. Routing nodes typically charge a small base fee plus a small percentage based on the payment size, which is usually far cheaper than the congested Bitcoin base layer.

Is the Lightning Network a separate cryptocurrency?No. The Lightning Network is not a separate coin or token. It is a technology layer that runs on top of the Bitcoin blockchain, using the same native asset to facilitate transactions rather than creating a new one.

How long does a Lightning transaction take?Lightning payments generally settle in milliseconds. Because transactions are verified off-chain through smart contracts rather than waiting for miners to process a block, speeds are typically comparable to or faster than traditional card networks.

What happens if a Lightning node goes offline?If a node goes offline, it simply cannot route new payments or update its channel balances. If a counterparty becomes unresponsive, the other party can broadcast the most recent valid commitment transaction to force close the channel and recover funds after a set delay.

Do I need to run a node to use the Lightning Network?No. Everyday users don't need to run a hardware node. Mobile wallets or centralized platforms manage the infrastructure, channel liquidity, and node connectivity, so users can send and receive from a smartphone.

FAQ

What is inbound liquidity, and why does it matter?Inbound liquidity is the amount of Bitcoin on your counterparty's side of a payment channel, which determines how much you can receive. Without it, you can only send funds outward. Modern wallets typically use LSPs to provide inbound capacity automatically when you try to receive a payment.

Can the Lightning Network handle large transactions?It's technically possible, but the network is primarily designed and optimized for smaller transactions. Large payments can fail if the routing path lacks capacity in an intermediate channel, though protocols like Multi-Part Payments allow a large payment to be split across multiple simultaneous routes.

What are Hash Time-Locked Contracts (HTLCs)?An HTLC is a type of smart contract used to route Lightning payments across multiple users without requiring them to trust each other. It ensures an intermediate node can only claim forwarded funds by proving the payment reached its final destination within a set timeframe.

How do Taproot Assets work on the Lightning Network?Taproot Assets is a protocol upgrade that allows unique digital assets, such as fiat-pegged stablecoins, to be issued directly on the Bitcoin blockchain. These assets can be deposited into Lightning channels and routed globally, converting across Bitcoin's existing liquidity to move different asset types quickly.

What is the difference between BOLT 11 and BOLT 12?BOLT 11 is the legacy invoice standard, requiring a server to dynamically generate single-use, time-bound payment requests. BOLT 12 is the newer standard, introducing static, reusable offers that support recurring payments, simple QR codes, and stronger privacy through route blinding.

Quick Glossary

BOLT (Basis of Lightning Technology): the community-driven specifications that define how different Lightning Network software implementations communicate.

Channel splicing: a feature that lets users add or remove funds from an active channel using a single on-chain transaction, without interrupting off-chain payments.

Commitment transaction: an off-chain Bitcoin transaction held by both parties in a channel, reflecting the current agreed distribution of funds.

Force close: the unilateral closure of a channel by broadcasting the latest commitment transaction, typically used when a counterparty is unresponsive or acting maliciously.

HTLC (Hash Time-Locked Contract): a conditional smart contract requiring the receiver to acknowledge payment with a cryptographic secret within a set timeframe to claim funds.

LSP (Lightning Service Provider): a node offering infrastructure services to participants, such as leasing inbound liquidity or automating channel opens.

Onion routing (Sphinx): a privacy-preserving method where routing information is encrypted in layers so no single node knows the full path or origin of a payment.

Key Takeaways

• The Lightning Network is a Layer 2 protocol that enables faster, lower-fee Bitcoin transactions by moving settlement off the main blockchain.
• Transactions happen within private, multi-signature payment channels, and Hash Time-Locked Contracts route payments securely across intermediaries.
• BOLT 12 offers and dynamic channel splicing have improved the user experience with reusable payment codes and more flexible liquidity management.
• Taproot Assets allows fiat-pegged stablecoins to be routed over Lightning, extending Bitcoin's rails to other asset types.
• Canadians can access the Lightning ecosystem by buying Bitcoin on a regulated domestic platform using Interac e-Transfer, then moving funds to a self-custodial mobile wallet.

Closing

Understanding the mechanics behind the Bitcoin Lightning Network helps explain one of the more significant infrastructure developments in cryptocurrency. As adoption continues and tools like BOLT 12 offers and Taproot Assets come online, interacting with the ecosystem is becoming more straightforward for everyday users. For Canadians exploring this technology, the first step is usually bridging traditional finance to digital assets by learning how to buy Bitcoin in Canada on a regulated platform before moving assets onto the Layer 2 network.