> For the complete documentation index, see [llms.txt](https://docs.kuma.bond/kuma-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kuma.bond/kuma-protocol/dao-and-governance/proposal-framework/kuma-improvement-protocol-kip.md).

# KUMA Improvement Protocol (KIP)

## 1. Writing a KIP

KIPs are about the most important modifications either on the governance framework, or on the protocol directly.

This type of proposal should include, in addition to all the points mentioned in the first part:

**Context:** (After summary)

 What’s the modification and why it’s needed.

KIPs would concern but wouldn’t be limited to:

* New version of the protocol
* Modification of a smart contract
* Updates on the initial parameters
* Modification of the governance framework
* Add/Remove a signer on the DAO multisig (will be introduced in the next few months)

KIPs are the most critical and important types of proposals, as it’s directly about the core product of KUMA Protocol or a major change in the functioning of governance.

## 2. Submission of proposal

It’s very important to get as much DAO members aware of this kind of proposal for them to vote accordingly, which is why we should consider more conservative parameters, and a longer voting period:

* Admin: Team multisig
* Quorum: 0,5% of the total supply (5M MIMO)
* Voting duration: 7 days


---

# 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.kuma.bond/kuma-protocol/dao-and-governance/proposal-framework/kuma-improvement-protocol-kip.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.