# Where to Go Next

Completing the Learn Bitcoin from the Command Line pathway means you now understand how to interact directly with Bitcoin Core through the command line.

You have worked with:

* Running and inspecting a node
* Constructing and analyzing transactions
* Working with multisig and PSBTs
* Exploring Bitcoin Script

Many learners use this pathway as a bridge between understanding Bitcoin and actively building with it.

Below are a few common next steps.

***

### Deepen Your Protocol Understanding

If you want to strengthen your conceptual understanding of the Bitcoin protocol, consider studying: [**Mastering Bitcoin**](https://pathways.btrust.tech/01)

This pathway explores the underlying systems that power Bitcoin, including:

* The Bitcoin transaction model
* Digital signatures and authorization
* Peer-to-peer networking
* Mining and consensus
* Bitcoin security assumptions

Combining CLI experience with protocol knowledge creates a strong foundation for Bitcoin development.

***

### Continue Exploring Bitcoin Core

The pathway covers Chapters 1–13 of Learning Bitcoin from the Command Line.&#x20;

[Chapters 14–20](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line) explore more advanced Bitcoin Core capabilities, including deeper RPC functionality and system-level interaction.

Many learners continue experimenting by:

* Running additional RPC commands
* Exploring wallet functionality in more depth
* Inspecting blocks and transactions in detail
* Testing Bitcoin Core behavior in different scenarios

Hands-on experimentation is one of the best ways to strengthen your understanding.

***

### Begin Exploring Bitcoin Development

Once you are comfortable interacting with Bitcoin Core, the next step is often to begin exploring Bitcoin development workflows.

You can start by:

* Running a local Bitcoin development environment
* Exploring Bitcoin Core source code
* Reading developer documentation
* Following discussions in Bitcoin developer communities

Understanding how Bitcoin software works internally is a natural next step after learning the CLI.

***

### Study a Bitcoin Development Language

Many developers working on Bitcoin tools and infrastructure use languages such as:

* Rust
* C++
* Python
* JavaScript

Builders pathways such as [**Rust for Bitcoiners**](https://pathways.btrust.tech/03) and [**Language Clubs**](https://pathways.btrust.tech/04) are designed to help developers begin building tools, libraries, and infrastructure around Bitcoin.

***

### Explore the Builders Resource Hub

The Builders [Resource Hub](https://pathways.btrust.tech/resource-hub) contains curated resources for developers entering the Bitcoin ecosystem.

This includes:

* Guides for making your first open-source contribution
* Developer tools and setup walkthroughs
* Curated Bitcoin open-source projects
* Code review and collaboration practices

Many learners use the Hub to begin identifying their first open-source contribution opportunities.

***

### Join the Builders Community

Learning Bitcoin development works best when you connect with others doing the same work.

In the Builders community you can:

* Discuss technical concepts
* Ask questions about development workflows
* Discover open-source opportunities
* Share your learning progress

Many contributors begin simply by participating in discussions and helping others understand concepts.

<a href="../../../../home#community" class="button primary">Join Our Community</a>

***

### Begin Contributing to Bitcoin Open Source

Once you are comfortable with the fundamentals, you may choose to explore contributing to open-source Bitcoin projects.

Common starting points include:

* Documentation improvements
* Testing and bug reports
* Small feature fixes
* Developer tooling improvements

Even small contributions help strengthen the ecosystem and build your experience.&#x20;

***

### A Note on Progress

Bitcoin development is a long-term journey.

Most contributors start by:

* Experimenting with Bitcoin software
* Reading documentation and code
* Asking questions in developer communities
* Making small improvements to open-source projects

Over time, these small steps build deep technical understanding and meaningful contributions.
