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

# Governance

MilkySwap utilizes a proposal system that is common amongst other DAOS & protocols. Proposals are known on our platform as MSIP (MilkySwap Improvement Proposal), each having its own designator such as MSIP-1, MSIP-2, MSIP-3 etc.&#x20;

Voting on the MilkySwap DAO requires users to possess **CREAMY**. The more **CREAMY** you hold, the greater voting power you have. If you wish to have greater voting power, you will need to churn more **MILKY** for a longer period of time to receive more **CREAMY.**

This voting mechanism will be important for which farms receive boosted modifiers.&#x20;

{% hint style="info" %}
For more information on churning **MILKY** for **CREAMY**, visit our [guide](https://milkyswap.gitbook.io/milkyswap/the-platform/churning)
{% endhint %}


---

# 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://milkyswap.gitbook.io/milkyswap/creamy/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.
