> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-4-proof-of-work-bitcoin-whitepaper.md).
# Section 4, Proof-of-Work (Bitcoin Whitepaper)
In this course, we break down [***Section 4 of the Bitcoin whitepaper, 'Proof-of-work'*****.**](https://learn.bsvblockchain.org/hubfs/Bitcoin%20white%20paper.pdf)
{% embed url="" %}
You will learn about the **fundamentals of Proof-of-work** and its critical role in blockchain technology. This course is designed to provide you with a comprehensive understanding of various concepts, mechanisms, and processes that underpin the Proof of Work system. By the end of this course, you will be equipped with the knowledge necessary to navigate and analyze the complexities of blockchain consensus mechanisms.
What you will learn:
* **Introduction to Proof-of-Work** and its significance in blockchain.
* The **Hashcash system** and the **hashing process** involved in mining.
* The concept of **difficulty adjustment** and how it ensures block validation.
* The **consensus mechanism** that allows nodes to agree on the state of the blockchain.
* The role of **honest nodes** in promoting chain growth and stability.
We invite you to join the course and engage with your peers in the forum to ask questions and share comments. Your participation will enhance your learning experience and foster a collaborative environment.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-4-proof-of-work-bitcoin-whitepaper.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
