# Suggested Weekly Pace

The self-paced pathway has no deadlines, but this suggested rhythm helps most learners maintain consistent progress.

You are free to move faster or slower.

***

### Week 1: Foundations

* [Chapter 1: Introduction](/01/mastering-bitcoin/study-materials.md#chapter-1-introduction)
* [Chapter 2: How Bitcoin Works](/01/mastering-bitcoin/study-materials.md#chapter-2-how-bitcoin-works) 

Focus on understanding:

* The double-spend problem
* Peer-to-peer architecture
* Bitcoin’s monetary design
* The difference between the protocol and the currency

> **Goal for the week**: *Understand the core problem Bitcoin solves and how a decentralized peer-to-peer system enables digital money without a central authority.*

***

### Week 2: Bitcoin Software

* [Chapter 3: Bitcoin Core: The Reference Implementation](/01/mastering-bitcoin/study-materials.md#chapter-3-bitcoin-core-the-reference-implementation) 
* [Chapter 4: Keys and Addresses](/01/mastering-bitcoin/study-materials.md#chapter-4-keys-and-addresses)

Focus on understanding:

* Bitcoin Core’s role in the ecosystem
* Public/private key cryptography
* Address derivation

> **Goal for the week**: *Understand how Bitcoin software interacts with the protocol and how cryptographic keys enable ownership and control of bitcoin.*

***

### Week 3: Wallet Mechanics

* [Chapter 5: Wallet Recovery](/01/mastering-bitcoin/study-materials.md#chapter-5-wallet-recovery)
* [Chapter 6: Transactions](/01/mastering-bitcoin/study-materials.md#chapter-6-transactions)

Focus on:

* Wallet architecture
* Transaction structure
* Inputs and outputs

> **Goal for the week**: *Be able to reason about how Bitcoin transactions are structured and how wallets manage funds and recovery.*

***

### Week 4: Authorization Systems

* [Chapter 7: Authorization and Authentication](/01/mastering-bitcoin/study-materials.md#chapter-7-authorization-and-authentication)
* [Chapter 8: Digital Signatures](/01/mastering-bitcoin/study-materials.md#chapter-8-digital-signatures) 

Focus on:

* Script fundamentals
* How Bitcoin proves ownership
* Signature verification

> **Goal for the week**: *Understand how Bitcoin authorizes transactions cryptographically and how digital signatures prove control of funds.*

***

### Week 5: Network Economics

* [Chapter 9: Transaction Fees](/01/mastering-bitcoin/study-materials.md#chapter-9-transaction-fees)
* [Chapter 10: The Bitcoin Network](/01/mastering-bitcoin/study-materials.md#chapter-10-the-bitcoin-network)

Focus on:

* Fee markets
* Node communication
* Transaction propagation

> **Goal for the week:** *Understand how Bitcoin’s network infrastructure and fee incentives coordinate transaction processing across nodes.*

***

### Week 6: Consensus Systems

* [Chapter 11: The Blockchain](/01/mastering-bitcoin/study-materials.md#chapter-11-the-blockchain)
* [Chapter 12: Mining and Consensus](/01/mastering-bitcoin/study-materials.md#chapter-12-mining-and-consensus)

Focus on:

* Block construction
* Proof-of-work
* Consensus rules

> **Goal for the week**: *Understand how Bitcoin achieves distributed consensus and maintains a secure global ledger without central coordination.*

***

### Week 7: Security and Scaling

* [Chapter 13: Bitcoin Security](/01/mastering-bitcoin/study-materials.md#chapter-13-bitcoin-security)
* [Chapter 14: Second-Layer Applications](/01/mastering-bitcoin/study-materials.md#chapter-14-second-layer-applications)

Focus on:

* Security assumptions
* Threat models
* Scaling approaches such as Lightning

> **Goal for the week**: *Understand Bitcoin’s long-term security model and how second-layer technologies enable scalability while preserving decentralization.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://pathways.btrust.tech/01/mastering-bitcoin/self-paced-learning/suggested-weekly-pace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.