# Protocol Specifications

Ninja Garden is an ecosystem created to optimise the churning of revenue where a portion of that revenue is passed back to our $KUNAI governance token holders. The following outlines our revenue pipeline:

* Operation of a Ninja Garden validator that yields 5% commissions
* Operation of the gINJ liquid staking derivative that yields a 2% exit tax for users who seek to unbond.
* Operation of a INJ-gINJ linear swap contract that takes 0.1% swap fees while facilitating liquidity for gINJ holders.
* Operation of a social-fi DAPP that sells keys where 4% trading fees is issued as protocol revenuve. (This is opposed to other Social-Fi where 5% of trading fees are issued to devs).
* Passive gINJ yield of \~17% APY that is generated by idle INJ resulting from purchased keys that are held and not actively traded.

With a simple TVL of $5 mil USD worth of INJ, our protocol will be generating close to $800k USD annually purely based on staking yields. Trading fees resulting from key trades and INJ-gINJ linear swaps will seek to supplement all of the above.

Protocol revenue that is generated is eventually passed back on to KUNAI holders. Once Ninja Garden has hit a sweet spot in terms of growth and size, emissions will be lowered dramatically to reward early KUNAI holders.


---

# Agent Instructions: 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:

```
GET https://ninja-garden.gitbook.io/ninja-garden/protocol-specifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.