Lightning moves payments off-chain, not off Bitcoin's rules

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

What the paper proposes

Joseph Poon and Thaddeus Dryja published 'The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments', draft version 0.5.9.2, on 14 January 2016. The paper's diagnosis is a capacity limit: at less than 7 transactions per second, Bitcoin's base chain cannot record every payment a global network would generate without either enormous blocks or trusting a custodian to net balances off-chain. Its proposed fix is a network of two-party payment channels funded by a single on-chain transaction, inside which balances update by exchanging signed transactions that are never broadcast unless a dispute forces one party to publish the chain's current state.

The blockchain as arbiter, not as the messenger

The paper is explicit that a channel is not a trusted overlay network; every balance update is a real bitcoin transaction, simply one both parties agree not to broadcast. What enforces honesty is a penalty structure: if a party broadcasts an old, since-superseded balance, the paper's construction lets the counterparty claim the entire channel balance as a penalty, enforced by the same base-layer validation rules the original whitepaper describes, provided that counterparty notices in time and broadcasts a competing breach-remedy transaction. The BOLT specifications that later formalised this design describe the same channels in enforceable protocol language, but the core assumption, that the base chain remains the final word when two parties disagree, is unchanged from the 2016 paper.

What noticing in time actually requires

That penalty only works if someone is watching. The paper states the requirement without softening it: a party must periodically monitor the blockchain to see if a counterparty has broadcast an invalidated commitment transaction, or delegate a third party to do so. A channel that nobody is watching, for however brief a lapse, is a channel where an old, more favourable balance can be published and the theft window can close before it is noticed. This is a genuinely different trust model from a single on-chain payment, which needs no ongoing attention once it has enough confirmations; a Lightning channel needs attention for as long as it stays open, or a paid third party to provide that attention instead.

• Who is responsible for watching a given channel, and what happens if that party goes offline?
• Does moving a payment off-chain change who bears the cost of dishonesty, rather than removing that cost?
• What does a channel's balance mean before either party has broadcast anything to the chain at all?

The paper's own framing is the useful one: Lightning does not remove Bitcoin's settlement layer, it defers contact with it, and deferred enforcement is not the same guarantee as immediate enforcement.