A Lightning watchtower is delegated breach monitoring. The channel participant gives it encrypted, transaction-specific data that becomes useful if a revoked commitment appears on-chain. The tower can then broadcast a justice or remedy transaction before the relative timelock expires.
In penalty-based Lightning channels, a dishonest peer might publish an earlier commitment that pays it more. The honest party can claim penalized outputs, but only during the CSV delay. A user who is offline throughout that window needs another observer.
A tower should not receive a readable history of every channel update. Designs commonly send encrypted blobs indexed by a compact hint derived from a potential breach transaction. A matching on-chain event supplies the information needed to decrypt and act.
The tower broadcasts a pre-signed response; it does not learn the client’s seed or gain general spending authority. Reward models may allocate part of the recovered value to the tower, while altruistic towers may operate without an on-chain reward.
A tower is useful only if it receives updates, watches the relevant chain and can propagate the remedy in time. Clients can use multiple independent towers and their own monitoring. Backup and tower state must advance as the channel state advances.
Watchtowers reduce an availability risk; they do not prevent every Lightning loss. They cannot repair a missing seed, a malformed backup, a compromised signing device or a breach for which they never received the matching blob. Protocol details also differ between implementations.
Primary or authoritative records make these details checkable: a Lightning watchtower monitors encrypted breach hints and can broadcast a pre-signed justice transaction when an old revoked channel state appears while the client is offline. They should be verified before using the coordinate in analysis.
The practical limit is: a watchtower does not hold ordinary spending keys or prevent every channel failure, and protection depends on backup updates, availability, reward design, fee conditions and protocol compatibility. A definition, office, chart pattern or published claim is not by itself a prediction or Bitcoin consensus rule.
For the clearest picture, read this entry together with Lightning Network, Payment Channel, Self-custody. The reverse links also lead from Payment Channel.