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

Contribution Rubric

Shared bar for a meaningful first Lightning contribution - scope, tests, and maintainer-ready communication.

intermediate3 days

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

./sign-in

On this page

Learning objectives

  • Score a Lightning contribution attempt against an explicit meaningful-PR rubric
  • Prefer docs, tests, and tooling issues before consensus-adjacent changes
  • Write maintainer-ready issue comments and PR descriptions for LND/CLN/LDK

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
Lightning contribution qualityreview rubricmeaningful PR Lightning

Step 1 // Required reading

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

  • docslightningnetwork/lnd CONTRIBUTING
  • docsElementsProject/lightning
  • articleConventional comments

Reflection prompts

  1. Which rubric rows would your planned Lightning PR fail today?
  2. What Polar/regtest evidence would you attach so reviewers can reproduce?
  3. How will you handle a request to shrink scope or add integration tests?

Lab // Rubric self-score

Complete Steps 2–3. Pick a real issue on LND, CLN, LDK, or a Lightning tool. Write a plan and self-score 0–2 on each rubric row before coding.

evidence required

  • ·Issue URL and approach doc
  • ·Rubric score table with notes
  • ·Draft first comment or PR body
  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.

Lightning contributions inherit Bitcoin’s review culture plus interop risk across implementations. Use the same meaningful-PR bar, with extra weight on reproduction notes.

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

Step 2 — Context: the ship bar

Row012
Problem fitVague / wrong daemonPlausible issueConfirmed issue + skill match
ScopeKitchen-sinkSlightly wideMinimal diff for one problem
CorrectnessUntestedManual onlyTest, Polar repro, or scripted check
CommunicationDrive-byBasic descriptionContext, risks, and review guide
CitizenshipIgnores project normsSkims guideFollows CONTRIBUTING + CI expectations

Ship bar: total ≥ 8/10 before requesting review.

Evidence pack for Pull / maintainers:

  1. Issue / PR URLs
  2. Rubric self-score
  3. Polar/regtest or unit test notes
  4. Interop note if behavior could differ across LND/CLN/LDK

Start smaller than you think

Docs, examples, and tests are excellent first Lightning PRs.

Done when: You can recite the five rows and the ≥ 8/10 ship bar.

Step 3 — Practice: score your plan (lab)

Pick a real issue. Write a one-page approach. Score each row 0–2. Draft the issue comment or PR body.

Checklist / anti-patterns

  • No untested protocol tweaks
  • No ignoring macaroon / permission surfaces in examples
  • No demanding merge timelines

Done when: Lab evidence (issue + score table + draft) is complete.

Next lesson

First Lightning PR — reproduce, test, open, and iterate with CI.

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

prevCode Review PracticenextFirst Lightning PR

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

No questions yet — be the first to ask.