> For the complete documentation index, see [llms.txt](https://moolanet.gitbook.io/moolanet-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moolanet.gitbook.io/moolanet-whitepaper/governance-mechanism/community-driven-governance.md).

# Community-driven Governance

MoolaNet's governance is a decentralized and community-driven process that allows token holders to actively participate in shaping the future of the protocol. The governance system is designed to ensure that decisions regarding protocol upgrades, parameter adjustments, and policy changes are made collectively by the community, rather than being controlled by a centralized authority.

MLA Token holders have the power to propose and vote on governance proposals, making them active participants in the decision-making process. The number of tokens held by an individual determines their voting power, giving more significant influence to those with a larger stake in the protocol.


---

# 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://moolanet.gitbook.io/moolanet-whitepaper/governance-mechanism/community-driven-governance.md?ask=<question>&goal=<endgoal>
```

`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.
