> 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/why-proof-of-stake-fails/the-delegated-proof-of-stake-band-aid.md).
# The Delegated Proof of Stake Band-Aid
**Delegated Proof of Stake (DPoS)** attempts to address PoS issues by introducing voting where token holders elect validators. However, this creates new problems:
* **Voter apathy**: Most users don't actively participate in governance
* **Name recognition bias**: Well-known validators maintain dominance by default
* **Circular entrenchment**: Popular delegates attract more stake, becoming more popular
* **No meritocratic selection**: Performance doesn't determine success—existing wealth does
New entrants have almost no chance of competing, as they cannot bootstrap enough stake to begin earning rewards.
**Summary**: PoS **sacrifices security, decentralization, and innovation for modest energy savings**—a catastrophic trade-off for enterprise applications.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/proof-of-work-the-only-viable-consensus-mechanism/why-proof-of-stake-fails/the-delegated-proof-of-stake-band-aid.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.