> For the complete documentation index, see [llms.txt](https://melaxy-docs.gitbook.io/melaxy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://melaxy-docs.gitbook.io/melaxy/gamefi-features/dao-governance.md). # DAO Governance Like Ethereum, Melaxy will be built into a decentralized metaverse for players to conduct DAO governance. In this vision, players can manage their own and their communityʼs battleships, planets, and other assets in a collaborative manner just like in the real world to achieve decentralized autonomy. **Governance feature of IFS token** The economic structure of the game itself is implemented by DAO governance at various levels, and the players who hold IFS tokens and contribute to the community are entitled to vote for decision-making in the community and the game, which makes IFS token have more value, and give players a sense of participation and belonging. At the **game governance**, players holding IFS are entitled to vote for: * Game development * Roadmap making * Revenue distribution * Other game and community related governance At the **guild governance**, IFS holders with a certain guild contribution can also decide: * Allocation of guild resources * The direction of guild development * The planning of the guildʼs planet construction * Use of guild funds * Other guild-related governance --- # 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://melaxy-docs.gitbook.io/melaxy/gamefi-features/dao-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.