> For the complete documentation index, see [llms.txt](https://sps.splinterlands.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sps.splinterlands.com/sps-chain/delegated-proof-of-stake-dpos.md). # Delegated Proof of Stake (DPoS) SPS Chain is governed via a Delegated Proof of Stake (DPoS) consensus model very similar to that of networks such as Hive, EOS, BSC, and many others. This means that any account with staked SPS tokens can vote for accounts that are running the SPS Chain software in order to elect the people or entities that will be responsible for validating all of the SPS Chain transactions and to determine who to entrust as SPS Treasurers that control the SPS Foundation funds. Please note that it will not cost anything or use up staked SPS in any way to vote for validators. It will simply be an additional use for staked SPS tokens and a way for token holders to participate in the governance of the system. Each block on the Hive blockchain is randomly assigned to one of the validators running the software based on the amount of staked SPS tokens they have voting on them. When assigned a block, the validator will publish a hash of the data in that block to the Hive blockchain which can then be checked and confirmed by all of the other validators. Once confirmed, the validator will receive a reward in SPS tokens for validating that block. The more staked SPS that is voting for a particular validator, the more blocks they will be assigned, and the more rewards they will receive. --- # 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://sps.splinterlands.com/sps-chain/delegated-proof-of-stake-dpos.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.