> For the complete documentation index, see [llms.txt](https://crono-king.gitbook.io/cronofi-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crono-king.gitbook.io/cronofi-finance/details/layer-2/usdkrono-layer-token.md).

# $KRONO - Layer Token

Introducing $KRONO, our first layered token that offers a unique anti-bot mechanism that **blacklist holders** who are using bots. This is to avoid the same scenario as seen in $CRONO where a couple of bots manage to secure a substantial amount of the initial supply, hindering the growth of $CRONO. Addresses that contain more than 5% of the supply will be flagged out and should they be deemed to be botting, they will be blacklisted.&#x20;

Furthermore, we will be implementing to incentivise HODL-ing instead of short term trading, further protecting the price of $KRONO. This taxation will be split into 2 components in the following manner:&#x20;

* Auto liquidity (3% will be used for adding liquidity to increase the depth of the pool)
* Burns (1% will be used for burns to reduce the supply available)

### Smart Tax

Unlike other protocols that simply tax token holders whenever a transaction was made, we managed to implement our smart tax feature that allows users to deposit, withdraw and harvest without incurring tax. Users will only be taxed when they are **BUYING or SELLING.**

### How does $CRONO holders benefit?

With a strong price for $KRONO, $CRONO are given the benefit to stake $CRONO with a higher multiplier and earn $KRONO. Furthermore, staking $CRONO will also contribute to our goal of 5m TVL for Eclipse day where we will be doing a 50k USDC worth of buyback and burns!&#x20;


---

# 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://crono-king.gitbook.io/cronofi-finance/details/layer-2/usdkrono-layer-token.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.
