Lightning Commitment Transaction

Overview

Meaning and scope

A Lightning commitment transaction is a pre-signed Bitcoin transaction representing one party’s enforceable view of a payment channel’s current balance. When a new state replaces an old one, revocation secrets make broadcasting the obsolete commitment punishable in traditional channels. Timelocks give the counterparty time to detect and respond.

Mechanism and operation

Each Lightning channel participant holds a commitment transaction that can close the channel on-chain according to the latest agreed state. Anchor outputs and fee-management mechanisms affect how closure transactions confirm. Lightning nodes must protect current commitments, revocation data, and channel backups, while watching the chain directly or through a watchtower. Payment services should distinguish off-chain HTLC settlement from final channel closure. Publishing a commitment can create multiple delayed or conditional outputs requiring further sweep transactions. In Lightning Commitment Transaction implementations, submission, peer acceptance, block inclusion, execution, confirmation, and finality provide different evidence, and a transaction can advance, stall, be replaced, or disappear from the canonical chain between those stages.

Practical payment example

Two Lightning participants update a channel balance after a purchase. Each retains the current enforceable commitment state and revocation data so an outdated channel state cannot be safely presented as the final settlement.

Operational checks

Repeated callbacks, node disagreements, reorganization, and delayed receipts must not create duplicate credits or irreversible state transitions before the required network evidence is available. Operational systems need idempotent processing keyed to stable transaction and business identifiers. Operational records should retain the raw transaction, network identifier, sender and destination, asset and amount, block reference, execution status, and observed timestamps.

Distinctions and limits

The two parties’ versions may use different output scripts while representing the same balance allocation and pending HTLCs. Lightning Commitment Transaction should be represented as a sequence of observable states rather than one success flag.

Related reading

Related definitions: transaction, block inclusion.