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.

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 issue Bitcoin OSS contribution 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

Explain Finding Good First Issues to a teammate without jargon - what problem does it solve?
What would break in production if you misunderstood Finding Good First Issues?
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)

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.

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.

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

Does the change solve the stated problem?
Are edge cases and rollout behavior covered?
Are tests or test vectors included?
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

prevPayment Processor API nextCode Review Practice

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.

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.

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.

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

Finding Good First Issues

Learning objectives

Step 1 // Required reading

Reflection prompts

Lab // Issue shortlist + plan

How to study this lesson

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

Step 3 — Practice: shortlist and plan (lab)

Checklist

Next lesson

further reading

Review club

Finding Good First Issues

Learning objectives

Step 1 // Required reading

Reflection prompts

Lab // Issue shortlist + plan

How to study this lesson

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

Step 3 — Practice: shortlist and plan (lab)

Checklist

Next lesson

further reading

Review club