Bitcoin VerityOpen comparator

Level 10 · Verification and second layers

Lightning channels, commitments and HTLCs

How two parties update a channel without an on-chain transaction for each payment, and why an old state becomes unsafe to publish.

Article
99
Reading time
18 minutes
Reviewed
10 September 2026

In a nutshell

A Lightning channel locks bitcoin in a funding output, then the parties exchange signed commitment transactions that can settle a state on chain. An HTLC ties payment to a secret and timeout. In classic penalty channels, revealing a revocation secret lets the counterparty punish publication of an obsolete state.

01

The funding output anchors the channel

Opening creates an on-chain funding transaction whose output is controlled under the negotiated channel type. Until that output is spent, balance changes can occur by exchanging signatures off chain.

Capacity is the bitcoin locked in the output, while directional liquidity changes. A party can send only what is available on its side; receiving requires usable liquidity in the opposite direction.

02

Each party holds a commitment

A commitment transaction spends the funding output and allocates the current state. Each side holds a version it can publish unilaterally, so scripts and keys are intentionally asymmetric.

Updates exchange new signatures before revoking the preceding state. Message order matters: neither party may be left without a valid close, or with two advantageously publishable states.

03

An HTLC combines hash and time

A Hashed Time-Locked Contract pays one branch when the payment-hash preimage is revealed before a deadline and permits a return path later. The same hash across hops gives the routed payment an atomic outcome.

Each intermediary uses a shifted CLTV expiry so that, after learning the secret, it has time to claim its incoming payment on chain if needed. An HTLC is a set of transaction conditions and protocol messages, not an autonomous legal contract.

04

An old state must be dangerous

In classic penalty channels, broadcasting an obsolete state exposes a delayed output to a counterparty holding its revocation secret. That party must notice and act within the relative timelock, or safely delegate monitoring.

A cooperative close uses an agreed settlement. A force close publishes the latest commitment and can require delays, extra on-chain transactions and fees. Channel recovery therefore depends on the implementation's state and backup model, not merely a seed phrase.

Level 10 · Verification and second layers

Terms to know

Funding output
The on-chain output holding a Lightning channel's capacity.
Commitment transaction
A pre-signed transaction able to settle a particular channel state on chain.
HTLC
A conditional payment claimed with a secret before a deadline or returned after it.

Common misconception

Lightning merely changes numbers on a server and has no enforceable connection to Bitcoin.

A more accurate explanation

Channel states are backed by signed Bitcoin transactions and scripts that either party can enforce on the base layer when closing.

A more accurate explanation

Why not put every payment on chain?

On-chain settlement is easier to audit but uses scarce block space and awaits confirmation. Channels move many updates off chain in exchange for online protocol, liquidity and more complex recovery.

99

Key takeaways

  1. 01A funding output anchors capacity on chain.
  2. 02A commitment lets either party close the current state.
  3. 03An HTLC combines a preimage with a timeout.
  4. 04Old penalty states require chain monitoring.

A child-friendly recap

In very simple terms

Two people lock bitcoin in a channel and then sign new balances without putting every payment in a block. An HTLC uses a secret and a timer so the whole payment can complete or return.

Reviewed: 10 September 2026

Sources and further reading

Sources support particular facts and definitions; listing one does not mean the editors endorse every view of its author.

01
Lightning Network white paperLightning Network
lightning.network
02
BOLT 2: channel management and HTLC updatesLightning Network Specifications
github.com
03
BOLT 3: channel Bitcoin transactionsLightning Network Specifications
github.com
04
BOLT 5: on-chain handlingLightning Network Specifications
github.com

Educational material, not an investment recommendation.