> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/architecture/consensus/voting-power.md). # Voting Power Representatives' voting power in [dPoS](/architecture/consensus.md) is determined by the amount of Keeta tokens delegated to them. When token holders delegate their Keeta to a representative, they increase that representative's voting power in the consensus process. Representatives with more delegated tokens have stronger voting power when deciding whether to add new blocks to the chain. This system ensures that those trusted with more of the network's tokens have greater influence in validation decisions, while still allowing smaller token holders to participate in governance by choosing which representatives to support through delegation. The mechanism creates a balance between network security and decentralized participation.

dPoS allows all participants to contribute to the voting process without requiring them to be representatives, and allows trustworthy parties to become representatives without personally holding substantial weight.

--- # 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://docs.keeta.com/architecture/consensus/voting-power.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.