> 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/in-game-governance.md). # Governance Voting System This page will describe the current SPS governance voting system that is in place as of the time of writing, which is around March of 2025. This system will continue to be improved and further decentralized over time as more of the infrastructure for the project is ready, most notably the SPS Chain and its Delegated Proof of Stake consensus mechanism which you can read more about in the [SPS Chain](/sps-chain.md) section of this document. Anyone is free to submit a governance proposal to a vote of all staked SPS token holders by publishing a post detailing their proposal to the Hive blockchain and including #spsproposal as the first tag on the post. Additionally, there is a fee for submitting a proposal of 100k DEC tokens. The fee must be paid by burning the tokens (transferring them to the "null" account in game), and the ID of the burn transaction on the Hive blockchain must be included by itself as the first line of the proposal post. Please note that the DEC burn transaction must have been made by the same account from which the proposal post is published. --- # 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/in-game-governance.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.