> For the complete documentation index, see [llms.txt](https://kernel-protocol.gitbook.io/kernel-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kernel-protocol.gitbook.io/kernel-protocol/tokenomics-and-revenue-model/kern-tokens-and-protocol-revenues.md).

# KERN Tokens & Protocol Revenues

At the heart of the Kernel Protocol ecosystem lies the KERN token. KERN tokens benefit from revenues accumulated by Kernel Protocol via a buy-back-and-burn mechanism. The tokens are also used to reward stakers during airdrop seasons.

Protocol revenue on Kernel Protocol is generated by taking a 0.1% minting fee and 0.25% redemption fee on all kAssets.

Protocol revenues are distributed as follows:

* 80% of fees generated are used for buy-back-and-burns of KERN tokens to ensure the token remains inflationary and to counterbalance any seasonal airdrops.
* 20% of fees go to project operations.


---

# 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://kernel-protocol.gitbook.io/kernel-protocol/tokenomics-and-revenue-model/kern-tokens-and-protocol-revenues.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.
