> For the complete documentation index, see [llms.txt](https://docs.idle.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idle.finance/governance/idle-dao/governance-guides/how-to-propose-an-iip.md).

# How to propose an IIP

Idle Improvement Proposals (IIPs) are the tool to let the Idle Governance implement new ideas in the Idle protocol through a transparent on-chain voting process. 

{% hint style="info" %}
IIPs are executed if the majority (50% +1) of the voters casts a “For” vote and at least 4% of the total voting right supply (520,000 IDLE) cast a vote on that proposal, either in favour or against. Community members can create a proposal if they have at least 130,000 IDLE as delegated votes and hold them during the entire voting process (up to the implementation).
{% endhint %}

Begin by starting a new post under the [IIP subcategory ](https://gov.idle.finance/c/proposals/iip/17)and include a clear, concise title beginning with **“\[IIP-#] - Your Title Here”**.

Bear in mind that your proposal will be better perceived and will lead to implementation if it is focused, includes sufficient background information, and has action points that are easy to understand. Additionally, please structure your proposal as modelled below.

![](/files/ADNin6VTJInxfjzbq03G)


---

# 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://docs.idle.finance/governance/idle-dao/governance-guides/how-to-propose-an-iip.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.