Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Upgrades and scaling · Entry 211

Lightning watchtowers: monitoring channels while a wallet is offline

AI-assisted research · separate automated verificationCorrections

Theme
Upgrades and scaling
Sources
7 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Lightning watchtowers: monitoring channels while a wallet is offline
FactDetailSource
Threat watchedPublication of a revoked channel state[1]
Protection pathAn on-chain response within applicable constraints[1][2]
Separate needWallet and channel recovery backups[3]
01

Why an old agreement needs a response

In the documented penalty-channel design, updated commitments supersede earlier agreements. Publishing a revoked state can trigger a penalty response. The affected party must detect the breach and act before the counterparty’s delayed output becomes spendable.

A watchtower can perform that monitoring role using prepared, encrypted information. The exact information it receives and the response it can make depend on the implementation.

02

A delay measured in blocks is not a fixed number of hours

Suppose a relevant delay is 144 blocks. At an assumed average of ten minutes per block, that corresponds to 24 hours on average. Actual blocks arrive irregularly, so it is not a guaranteed 24-hour response window.

The tower must be available and able to get the protective transaction confirmed under the relevant conditions. Merely entering a tower address in an interface is not evidence that current channels are covered.

03

Keep monitoring separate from recovery and routing

A tower is not a substitute for the seed and channel backup required after device loss. It also does not keep every peer online, create receiving capacity or repair an invalid invoice.

Check the implementation’s coverage and connection status, and keep its normal backup process. The cited LND-oriented guide explains one tower design; other channel and wallet designs can have different requirements.

Direct answers

Questions people ask

Can a watchtower restore my missing seed?

No. Its breach-monitoring role is different from key recovery. Keep the recovery material required by the wallet and implementation.

Does a watchtower make all offline Lightning payments work?

No. Monitoring for revoked commitments does not supply an online payment recipient or a usable payment route. Payment availability is a separate issue.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

A Lightning watchtower monitors the blockchain for a specific kind of channel breach: a counterparty publishing an old, revoked commitment. With the necessary information, it can submit the protective transaction while the user’s node is offline. It does not recover every lost wallet, provide missing routing liquidity or ensure that every payment succeeds. Its protection depends on the tower setup, channel design and timely on-chain action.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Threat watched: Publication of a revoked channel state

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Protection path: An on-chain response within applicable constraints

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Separate need: Wallet and channel recovery backups

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. WatchtowersLightning Labs

    Monitoring revoked channel states and limitations of outsourced breach protection.

    Locator: Channel breaches; Watchtowers; Timelocks · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.295ZOpen source
  2. BOLT 3: Bitcoin Transaction and Script FormatsLightning specification contributors

    Commitment output delays and conditional HTLC settlement on chain.

    Locator: Commitment Transaction; HTLC Outputs; Closing Transaction · Version / scope: Pinned BOLTs revision · Retrieved: 2026-10-02T18:53:57.097ZOpen source
  3. Recovery: Planning for FailureLightning Labs

    LND seed, static channel backups, safe channel recovery and external backups.

    Locator: aezeed; Static channel backups (SCB); Channel Database · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.272ZOpen source
  4. The lifecycle of a payment channelLightning Labs

    Cooperative versus unilateral closes and confirmation/delay requirements.

    Locator: Opening a channel; Sending funds through a payment channel; Closing a channel; Cooperatively; Non-cooperatively · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.295ZOpen source
  5. Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi Nakamoto

    Independent hash attempts, incentives, transaction collaboration limits and Poisson block-arrival approximation.

    Locator: Sections 4, 6, 7, 10 and 11 · Version / scope: 2008 paper · Retrieved: 2026-10-02T18:53:58.187ZOpen source
  6. Sending PaymentsLightning Labs

    LND initiated/in-flight/succeeded/failed statuses and safe retry semantics.

    Locator: Pathfinding; Dispatching Payments; Payment Fees; Monitoring Payments · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.437ZOpen source
  7. The payment cycleLightning Labs

    Invoice-first Lightning flow, routes and settlement preimages.

    Locator: Introduction: sender and receiver interaction; Create invoice; Make the payment; Check the payment; Other payment types · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.281ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Lightning watchtowers: monitoring channels while a wallet is offline.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/lightning-watchtowers/