> 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/proof-of-work-the-only-viable-consensus-mechanism/introduction-to-proof-of-work-superiority/the-scalability-misconception-debunking-the-myth.md). # The Scalability Misconception: Debunking the Myth ### The False Narrative A common criticism claims that **Proof-of-work (PoW) is inherently unscalable and energy-intensive**. This belief has shaped blockchain development for years, driving projects toward alternative consensus mechanisms. However, this criticism stems from observing **artificially limited implementations** rather than examining PoW's actual capabilities. **Bitcoin Core (BTC)** maintains an artificial **1MB block size limit**, which was originally introduced as a temporary spam prevention measure. This constraint was never lifted, creating a bottleneck that processes only **4-7 transactions per second (TPS)**. When critics evaluate PoW's energy efficiency, they use BTC as their benchmark—but this is like judging the potential of automobiles by observing one with its parking brake engaged. --- # 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/proof-of-work-the-only-viable-consensus-mechanism/introduction-to-proof-of-work-superiority/the-scalability-misconception-debunking-the-myth.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.