# Lightning watchtowers: monitoring channels while a wallet is offline 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [BOLT 3: Bitcoin Transaction and Script Formats](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/03-transactions.md) Canonical: https://degreesofsatoshi.com/encyclopedia/lightning-watchtowers/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Threat watched:** Publication of a revoked channel state ([Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md)) - **Protection path:** An on-chain response within applicable constraints ([Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [BOLT 3: Bitcoin Transaction and Script Formats](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/03-transactions.md)) - **Separate need:** Wallet and channel recovery backups ([Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md)) ## 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md) ## 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [BOLT 3: Bitcoin Transaction and Script Formats](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/03-transactions.md); [Bitcoin: A Peer-to-Peer Electronic Cash System](https://bitcoin.org/bitcoin.pdf) ## 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md); [Sending Payments](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/payments.md) ## Questions ### 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md) ### 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. Evidence: [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md); [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md) ## Claims and scope ### lightning-watchtowers-quick-answer 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: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### lightning-watchtowers-fact-threat-watched Threat watched: Publication of a revoked channel state Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### lightning-watchtowers-fact-protection-path Protection path: An on-chain response within applicable constraints Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### lightning-watchtowers-fact-separate-need Separate need: Wallet and channel recovery backups Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Watchtowers](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/watchtowers.md) — Lightning Labs. Monitoring revoked channel states and limitations of outsourced breach protection. Locator: Channel breaches; Watchtowers; Timelocks. Retrieved: 2026-10-02T18:53:57.295Z. - [BOLT 3: Bitcoin Transaction and Script Formats](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/03-transactions.md) — Lightning specification contributors. Commitment output delays and conditional HTLC settlement on chain. Locator: Commitment Transaction; HTLC Outputs; Closing Transaction. Retrieved: 2026-10-02T18:53:57.097Z. - [Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md) — Lightning Labs. LND seed, static channel backups, safe channel recovery and external backups. Locator: aezeed; Static channel backups (SCB); Channel Database. Retrieved: 2026-10-02T18:53:57.272Z. - [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md) — Lightning 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. Retrieved: 2026-10-02T18:53:57.295Z. - [Bitcoin: A Peer-to-Peer Electronic Cash System](https://bitcoin.org/bitcoin.pdf) — Satoshi Nakamoto. Independent hash attempts, incentives, transaction collaboration limits and Poisson block-arrival approximation. Locator: Sections 4, 6, 7, 10 and 11. Retrieved: 2026-10-02T18:53:58.187Z. - [Sending Payments](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/payments.md) — Lightning Labs. LND initiated/in-flight/succeeded/failed statuses and safe retry semantics. Locator: Pathfinding; Dispatching Payments; Payment Fees; Monitoring Payments. Retrieved: 2026-10-02T18:53:57.437Z. - [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md) — Lightning 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. Retrieved: 2026-10-02T18:53:57.281Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry 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/