> For the complete documentation index, see [llms.txt](https://docs.deso.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deso.org/deso-governance.md). # DeSo Governance Changes to the DeSo blockchain happen according to upgrades to its Revolution PoS consensus mechanism, which is described in detail [here](https://revolution.deso.com/) and [here](https://docs.deso.org/deso-validators/run-a-validator), with all current validators and their staking percentages listed on [the DeSo block explorer here](https://explorer.deso.com/validators). In simple terms, anyone can submit an upgrade to [DeSo’s fully open-source code](http://github.com/deso-protocol/core), but an upgrade to the DeSo blockchain goes through only if 2/3rds of the validators (weighted by stake) upgrade their software before a particular block height. This is similar to how other Proof of Stake blockchains work, such as Ethereum, and it ensures that changes to the blockchain get heavy oversight and buy-in from the major economic players in the ecosystem before they go through. For the avoidance of doubt, it is impossible to upgrade the DeSo blockchain without a 2/3rds stake-weighted majority accepting the changes, noting that the DeSo blockchain is [fully 100% open-source](https://github.com/deso-protocol/core), and that no individual owns more than 20% of the DESO in existence. Learn about the key repos and how the code works [here](https://docs.deso.org/~/changes/fDLjGJdJathPNuf23Eol/deso-repos/architecture-overview) (outdated but good) and [here](https://docs.deso.org/~/changes/fDLjGJdJathPNuf23Eol/openfund/algorithmic-trading/debugging-tips-and-code-walkthrough). --- # 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://docs.deso.org/deso-governance.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.