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 // bitcoin

Finding Good First Issues

Identify beginner-friendly issues in Bitcoin repositories and plan your approach.

intermediate1 week

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

./sign-in

On this page

Learning objectives

  • Map major Bitcoin repositories and contribution surfaces
  • Select an issue that matches your skills
  • Write a short implementation plan before coding

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
good first issueBitcoin OSScontribution discovery

Step 1 // Required reading

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

  • docsbitcoin/bitcoin

    Core repo - steep bar; study issue labels and CONTRIBUTING before picking.

  • articleBitcoin Optech

Reflection prompts

  1. Explain Finding Good First Issues to a teammate without jargon - what problem does it solve?
  2. What would break in production if you misunderstood Finding Good First Issues?
  3. Which BIP, book chapter, or Core doc is authoritative here, and what did you verify?

Lab // Issue shortlist + plan

Complete Steps 2–3. Shortlist 2–3 issues (Review Club, /discover, or a labeled GFI), pick one that matches your skills, and write a short approach before coding.

evidence required

  • ·Issue URL(s) with one selected as primary
  • ·Written approach (problem, files likely touched, how you will test)
  • ·Self-score against the meaningful-PR rubric (preview is fine; full rubric next lessons)
  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.

Contributing starts with choosing the right battlefield. “Good first issue” labels help, but judgment matters more.

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

Step 2 — Context: where to look and how to scope

A too-hard first PR burns motivation. A too-vague issue stalls. Builders who scope well ship.

Where to look:

  • Bitcoin Core (steep, high bar)
  • rust-bitcoin, BDK, bitcoinjs-lib
  • Indexers, explorers, docs sites, Optech

Loading diagram…

Match skills → repo → issue → plan → communicate → code.

Docs and tests count

Clarifying docs or adding a regression test is a legitimate first contribution.

Start with Review Club picks on this lesson — especially Bitcoin Core GFIs and BDK docs issues — or explore /discover.

Done when: You can name one repo that fits your stack and why Core might wait.

Step 3 — Practice: shortlist and plan (lab)

Pick 2–3 candidate issues. Select one. Write: problem statement, likely files, test plan. Leave or draft an issue comment only when the plan is coherent — do not claim the issue prematurely.

Checklist

  • Issue matches a skill you already practiced on Pull
  • Scope is one problem, not a drive-by refactor
  • You know how you will prove it works (test/CI/manual)

Done when: Lab evidence (URLs + approach + draft self-score) is complete.

Next lesson

Code Review Practice — review others’ PRs with a maintainer mindset.

further reading

  • docsrust-bitcoin

review // club

Review club

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

  • Bitcoin Core good first issues

    Shortlist two Core GFIs and score them against the meaningful-PR rubric before commenting.

    gfi
    scoperepro steps
    25 min·advancedopen on GitHub

  • Bitcoin Core CONTRIBUTING guide

    Read Core's contribution guidelines and note how PR scope, review culture, and CI differ from typical web repos.

    spec review
    workflowtestingscope
    35 min·beginneropen 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

prevPayment Processor APInextCode Review Practice

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

No questions yet — be the first to ask.