> 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-integration-request-kir.md).

# KUMA Integration Request (KIR)

## 1. Proposing a new NFT Bond

As with all governance upgrades, KIR Template is recommended.

**Bonds Presentation :** (examples)

* `riskCategory` Unique risk category identifier computed with keccack256(abi.encode(currency, country, term)) - each token belongs to a single riskCategory
* `cusip-isin` Identification number of the underlying bond
* `principal` Bond face value  
* `coupon` Annual interest rate paid on the bond per - rate per second
* `issuance` Bond issuance date - timestamp in seconds
* `maturity` Date on which the principal amount becomes due - timestamp is seconds 
* `term` Lifetime of the bond ie. maturity in seconds - issuance date - example : 10 years 
* `country` Treasury issuer - example : US
* `currency` Currency of the bond - example : USD 

## 2. Submission of proposal

The proposal can now be submitted on [Snapshot](https://snapshot.org/#/mimo.eth), including all the information from the above steps.

Considering that the integrations proposals can happen quite often and that the risk for the protocol is lower than other proposal types, we could consider the following parameters:

* Admin: DAO Multisig
* Quorum: 0.1% of the total supply (1M vMIMO)
* Voting Duration: 3 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-integration-request-kir.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.