RoadmapsProjects
Sign in./start

Learn

RoadmapsProjects

Contribute

DiscoverIssues

Account

Sign in./start-building

Become an Open Source Builder. Learn. Build. Contribute.

Learn

RoadmapsProjectsStart Building

Contribute

DiscoverIssues

Account

Sign inDashboardSettings

Legal

PrivacyTerms

© 2026 Pull // all rights reserved

PrivacyTerms

lesson // lightning

Watchtowers

Outsource breach detection so offline wallets stay protected.

advanced5 days

Public lesson — sign in to track progress on this roadmap.

./sign-in

On this page

Learning objectives

  • Explain the watchtower threat model
  • Describe encrypted breach remedies at a high level
  • Configure or integrate a tower in a lab

study // plan

Lessons are primers. Depth comes from required reading, interactive labs, reflection, and a hands-on check with evidence — the BOSS study pattern.

Research on Bitcoin Search

Required reading

  • bookMastering the Lightning Network

    Ch. 16: Security and Privacy

Reflection prompts

  1. Explain Watchtowers to a teammate without jargon — what problem does it solve?
  2. What would break in production if you misunderstood Watchtowers?
  3. Which BOLT (or implementation doc) is the source of truth for this topic, and what did you verify there?

Lab // Polar check

After reading, run one hands-on check related to Watchtowers. Prefer local regtest or Polar over mainnet.

evidence required

  • ·Command output or screenshot from your local lab
  • ·One sentence on what you observed vs expected
  • ·Link to the required reading section you used

A watchtower monitors the blockchain for revoked commitment broadcasts on your behalf and can publish justice transactions if you are offline.

Why this matters

Phones sleep. Laptops close. Lightning’s penalty model needs someone watching. Towers extend security to intermittent devices.

Analogy

A neighborhood security camera that only unlocks the evidence locker if a specific break-in pattern appears, and it does so without learning your daily life.

Loading diagram…

Towers watch for breaches and act when you cannot.

Trust tradeoffs

Towers learn some metadata. Design privacy expectations; consider multiple towers.

Worked mental model

Re-read the diagrams in this lesson once out loud in plain language. If you cannot explain the flow to a friend without jargon, pause and revisit Mastering Bitcoin / Mastering Lightning chapters linked in Resources. Chapter references are intentional, not decorative.

Hands-on habit

Every protocol idea should be paired with one local experiment:

  1. Reproduce the happy path on regtest (or Polar for Lightning)
  2. Break it on purpose (wrong fee, expired invoice, offline peer)
  3. Write down what error you saw and which layer produced it (wallet, node, mempool, peer)

That habit turns reading into builder instinct.

Glossary check

Pick three terms from this lesson and define them in one sentence each without opening notes. Weak definitions mean the lesson is not finished yet.

Resource order

Use Resources in order: narrative book chapter first, then BIP/BOLT for precision, then implementation docs for commands. Jumping straight to RPC flags without the mental model creates brittle knowledge.

Next steps

Build a Lightning POS: invoices, webhooks, and settlement UX.

further reading

  • docsLND watchtower
  • articleBitcoin Optech: Watchtowers

progress // sign in

Reading is public. Sign in to mark lessons complete, sync across devices, and unlock your roadmap.

./sign-in-to-track
prevLDKnextLightning POS

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.