> 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/bitcoin-whitepaper-abstract/cpu-power-and-ledger-integrity.md).
# CPU Power and Ledger Integrity
*The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power.*
\- Satoshi Nakamoto, Bitcoin Whitepaper
This concept emphasizes that the integrity of the Bitcoin ledger is maintained **through the collective computational power of the network**.
At scale, **the capacity of nodes** to solve the difficult proof-of-work problem is crucial, as nodes must also keep pace with the rest of the network in downloading, validating, and storing all transactions occurring in real-time.
The hashing machinery used to solve proof-of-work effectively votes for **the most capable node**, **incentivizing operators to invest in the fastest and most efficient machines** to attract the most hash power. This dynamic ensures that **the network remains healthy**, as node operators are motivated to invest in superior infrastructure to enhance their capacity for validating transactions and maximizing fee revenue.
---
# 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/bitcoin-whitepaper-abstract/cpu-power-and-ledger-integrity.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.
