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

Builder Portfolio

Document your projects and contributions in a public Pull profile.

intermediate5 days

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

./sign-in

On this page

Learning objectives

  • Present projects with problem, approach, and results
  • Link verifiable commits and PRs
  • Write a short builder narrative without hype

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
builder portfolioGitHub profilecontribution tracking

Step 1 // Required reading

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

  • docsGitHub profile README

Reflection prompts

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

Lab // Portfolio draft

Complete Steps 2–3. Draft or update your Pull profile / public writeup with at least one project, one PR or commit link, and a short builder narrative without hype.

evidence required

  • ·Link to Pull profile or public portfolio page
  • ·Links to project(s) and PR(s) / commits cited
  • ·Short narrative (problem → approach → result) for one artifact
  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.

Your portfolio is evidence: repositories, PRs, writeups, and demos. Hiring managers and OSS maintainers trust artifacts over adjectives.

Complete Step 1 // Required reading in the study plan above, then continue here. This closes the Bitcoin roadmap’s open-source chapter.

Step 2 — Context: what to include

  • Mini wallet / explorer / processor links
  • 2–3 merged (or deeply reviewed) PRs
  • A diagram of architecture for one project
  • Regtest demo script or short recording

Loading diagram…

Artifacts compose into a credible builder profile.

Prefer depth over volume

One well-documented wallet beats ten empty repos named bitcoin-bot.

Done when: You can name the three artifact types you will show first.

Step 3 — Practice: ship the draft (lab)

Update your Pull profile (or public README). For one flagship artifact, write problem → approach → result. Link verifiable commits/PRs.

Checklist

  • At least one project with a clear problem statement
  • At least one verifiable PR or commit URL
  • Narrative without hype or unverifiable claims

Done when: Lab evidence (profile link + citations + narrative) is complete. Complete the chapter quiz when prompted.

Next lesson

Begin the Lightning roadmap — channels, invoices, and off-chain Bitcoin payments (/roadmaps/lightning).

further reading

  • articleConventional Commits
  • articleBitcoin Optech

review // club

Chapter review picks

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

  • BDK documentation pull requests

    Review a BDK docs PR and note whether examples would help a mini-wallet builder.

    pr review
    examplesAPI clarity
    35 min·beginneropen on GitHub

  • Recent Bitcoin Core PR for review practice

    Pick a small open Core PR and leave a conventional comment on one concrete improvement.

    pr review
    correctnesstestsscope
    45 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.

discussion

Discussion

prevMaintainer Collaboration

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

No questions yet — be the first to ask.