Feedback
Sign in./start

Site navigation

Theme

Learn

  • Roadmaps

Build

  • Projects
  • Developer Tools

Contribute

  • Open Source Projects
  • Issues
  • Reviews
  • First Contribution
  • BountiesSoon
  • Feedback

Prove

  • Builders

Ecosystem

  • Partners
  • Get Funded↗
  • HackathonsSoon
Sign in./start-building

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

Feedback welcome — open a GitHub issue.

Learn

RoadmapsStart Building

Build

ProjectsDeveloper Tools

Contribute

Open Source ProjectsIssuesReviewsFirst ContributionSupportFeedback

Prove

Builders Directory

Account

Sign in

Legal

PrivacyTermsCredits

© 2026 Pull // code MIT · curriculum CC BY-SA 4.0

PrivacyTermsCredits

lesson // lightning

LND

Build integrations with LND gRPC, REST, and macaroon authentication.

advanced2 weeks

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

./sign-in

On this page

Learning objectives

  • Run LND against bitcoind in a lab
  • Authenticate with macaroons safely
  • Call key RPCs for invoices, payments, and channels

study // plan

Lessons are primers. Start with Step 1 (required reading) when present, then follow the numbered steps in the article. Depth comes from primary sources, labs, reflection, and evidence.

Research on Bitcoin Search
LNDgRPC LightningmacaroonLightning daemon

Step 1 // Required reading

Complete these before the numbered steps in the lesson body. Links are listed here once — not repeated below.

  • bookMastering the Lightning Network

    Ch. 4: Lightning Node Software

  • docsLND documentation

Reflection prompts

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

Lab // LND invoice round-trip

Complete Steps 2–3. On Polar/regtest with LND, run getinfo, create an invoice, and pay it from a peer. Note how macaroons/TLS are configured.

evidence required

  • ·getinfo + addinvoice/payinvoice (or Polar) proof
  • ·One sentence on macaroon scope (admin vs readonly) for your app
  • ·Link to LND docs or Ch. 4 section you used
  1. 01

    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 the Mastering Bitcoin / Mastering Lightning chapters linked in Resources. Chapter references are intentional, not decorative.

  2. 02

    Hands-on habit

    Every protocol idea should be paired with one local experiment. That habit turns reading into builder instinct.

    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)
  3. 03

    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.

  4. 04

    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.

LND is a widely deployed Lightning implementation with gRPC/REST APIs and macaroon-based auth. Many apps integrate here first.

Complete Step 1 // Required reading in the study plan above, then continue here. This opens Implementation.

Step 2 — Core idea: APIs behind macaroons

Production integrations live or die on auth scoping, idempotent payment calls, and careful macaroon storage.

Analogy: Macaroons are VIP wristbands with permissions printed on them. Anyone holding an admin wristband is you — guard them like passwords.

Loading diagram…

Apps authenticate to LND; LND talks to Bitcoin and peers.
lncli getinfo
lncli addinvoice --amt 1000
lncli payinvoice <bolt11>

Macaroon hygiene

Do not commit macaroons. Use readonly macaroons for UIs that only display data.

Done when: You can name gRPC/REST + macaroon as the integration surface and one auth footgun.

Step 3 — Try it: invoice round-trip (lab)

On Polar LND nodes (or local): getinfo, create invoice, pay from peer. Note TLS + macaroon paths (do not paste secrets into notes).

Done when: Lab evidence (round-trip + macaroon scope sentence + source) is complete.

Next lesson

Core Lightning — plugins, hooks, and a lean daemon model.

further reading

  • docsLightning Terminal / Loop

review // club

Review club

Practice on real Lightning OSS changes tied to this chapter. Read the diff, use the checklist, and optionally paste your review comment URL in your lab notes.

  • LND good first issue

    Shortlist two GFIs and write a one-paragraph approach for the better fit.

    gfi
    scopetests
    25 min·intermediateopen on GitHub
review checklist
  1. Does the change solve the stated problem?
  2. Are edge cases and rollout behavior covered?
  3. Are tests or test vectors included?
  4. Is the diff minimal and clearly explained?

More repos and GFIs on /discover and /issues.

progress // sign in

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

./sign-in-to-track

discussion

Discussion

prevLightning Attack SurfacenextCore Lightning

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

No questions yet — be the first to ask.