24 useful places to learn, experiment, design and contribute. Each comes with a small next step you can turn into evidence of your work.
An interactive Bitcoin adventure that teaches through programming exercises, puzzles and simulations.
Complete an early lesson and explain one transaction concept in your own words.
Free, open-source learning project.
Explore resource ↗The third-edition book repository offers a substantial programming-oriented introduction to Bitcoin.
Pair a chapter with a small experiment and publish a reproducible notebook.
Read the repository’s edition and licensing notes.
Explore resource ↗A route into Bitcoin open-source development, with learning resources and examples of contributors’ work.
Use the self-paced seminar materials to organize a reading and discussion session.
Check current program intake separately; alumni stories are not placement guarantees.
Explore resource ↗Bitcoin protocol education spanning introductory material, developer basics and advanced subjects.
Choose a course that matches your experience and turn one exercise into a short technical explanation.
Course formats, prices and cohort dates vary; check the provider.
Explore resource ↗An India-rooted Bitcoin education community with study cohorts, review clubs and fellowship information.
Prepare questions for a study session, then contribute a useful set of notes.
Check each program’s current schedule and eligibility.
Explore resource ↗An engineering program for African developers moving into open-source Bitcoin and Lightning work.
Compare your public code and available study time with the application criteria.
The page asks for 3+ years of production experience and at least 20 hours a week. Confirm current intake.
Explore resource ↗A desktop tool for creating local Bitcoin and Lightning test networks with multiple node implementations.
Build a three-node network and document a successful payment and a failed route.
Local regtest development; requires Docker and its documented dependencies.
Explore resource ↗Open-source libraries for building Bitcoin wallet applications across platforms.
Make a test-wallet balance view and document how the app obtains chain data.
Choose current library versions and follow their own setup documentation.
Explore resource ↗A modular toolkit for adding Lightning functionality with control over key integration choices.
Compare LDK’s integration approach with the simpler LDK Node starting point.
Node operation and application integration require separate design decisions.
Explore resource ↗A home for Bitcoin-focused Rust libraries and a cookbook of development examples.
Write a small transaction-inspection utility with tests for malformed input.
Use documentation matching the exact crate version in your project.
Explore resource ↗Documentation for an open-source, self-hosted Bitcoin payment processor.
Map a test checkout from invoice creation to payment confirmation and order fulfillment.
Software and documentation are open source; hosting and operations still need a plan.
Explore resource ↗Ark and Lightning application demos, including wallet examples for several mobile and app frameworks.
Inspect a demo in your preferred language and document its network and server assumptions.
Check each demo’s network. Do not assume every example is a signet-only application.
Explore resource ↗A community guide covering Bitcoin product design, user research, accessibility and wallet flows.
Audit one receive-payment flow against its relevant guidance and explain your tradeoffs.
Reference guidance should be adapted to the product and its users.
Explore resource ↗Reusable Bitcoin interface components and screens for exploring product ideas in Figma.
Prototype an invoice that can be pending, paid or expired, with clear recovery actions.
Check the kit’s current instructions, account requirements and license.
Explore resource ↗A Bitcoin-oriented icon set with source files and formats useful in interfaces.
Use a small, consistent icon vocabulary and pair unfamiliar actions with text labels.
Review licensing and attribution for the assets you use.
Explore resource ↗Bitcoin Design’s collection of code resources connects interface ideas with implementation examples.
Select one component and demonstrate keyboard access, error states and responsive behavior.
Individual projects have their own maintenance status and licenses.
Explore resource ↗Technical newsletters, topic explanations and workshops about Bitcoin engineering developments.
Choose one topic relevant to a project and trace its original discussion before proposing a change.
A proposal described in a newsletter may not be deployed or widely supported.
Explore resource ↗The public repository of Bitcoin Improvement Proposals and their recorded status.
Read a proposal’s motivation, specification and status before implementing a related feature.
A BIP number or repository entry does not mean network adoption.
Explore resource ↗The evolving Lightning specifications, including messaging, routing and payment encoding.
Trace one field from a test invoice to its specification and your implementation’s behavior.
Specifications and implementations evolve; record the revision you consulted.
Explore resource ↗Prepared pull-request discussions that help newcomers learn code review and the Core codebase.
Reproduce an archived session’s test and write down what you verified and what remains unclear.
Use the archive anytime; check the site for actual upcoming meetings.
Explore resource ↗Review discussions and notes for people learning to contribute to LDK.
Choose a documented review, inspect the patch and explain one behavior it changes.
An archive is useful even when no upcoming meeting is announced.
Explore resource ↗The project’s own instructions for participating in Bitcoin Core development and review.
Read the current process, reproduce an issue, and submit evidence only when you can explain it.
Follow the project’s contribution and disclosure procedures.
Explore resource ↗An open design community working on resources and experiences for Bitcoin products.
Review a project’s existing discussion, then offer a focused flow analysis or research question.
Check the community’s current participation channels and contribution guidance.
Explore resource ↗A forum for detailed Bitcoin technical discussions and research.
Summarize one thread’s assumptions, unresolved questions and proposed experiments for your own notes.
Discussion is not consensus or evidence that a feature is ready for production.
Explore resource ↗No matching resources. Try a broader term or clear the filters.
Keep a short record of the problem, your decisions, what you tested and the limitations. A clear explanation makes a small project easier to evaluate.
Build your Bitcoin CV →These are editorial suggestions, not sponsored placements or audited software recommendations. Use each project’s current documentation, license and release notes. Test examples in their intended environment.