> 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-tokenomics/designed-for-the-end-game.md). # Designed for the End-Game When the DeSo Blockchain was first being built, it was designed from the ground up for what the team refers to as "the end-game." Every incentive has been intensely scrutinized, and designed to be robust under a state in which the blockchain has become mature, dominant, and structurally important. It is difficult to see the impacts of these design decisions now because we are in the early days of crypto, but we believe that the difference between strong tokenomic incentives and weak ones will have major impacts on society depending on which blockchain ends up winning, and we have taken this extremely seriously from the very beginning. --- # 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-tokenomics/designed-for-the-end-game.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.