> 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

Governance > Idle DAO > Guides > 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.

![](https://4022236167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lw-v0NTae0RVW1spR9R%2Fuploads%2Fukr1fA2Xkqurhx3fvKKm%2Fimage.png?alt=media\&token=fdbd30b2-5a5c-47f8-b7a0-b5e07a8ce01b)


---

# 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.idle.finance/governance/idle-dao/governance-guides/how-to-propose-an-iip.md?ask=<question>&goal=<user_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.