> For the complete documentation index, see [llms.txt](https://konra-project.gitbook.io/konra-dogechain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://konra-project.gitbook.io/konra-dogechain/konra-2.0.md).

# Konra 2.0

Konra on DogeChain is very much Konra 2.0, as we have learned many lessons in tokenomics and how to best launch initially on a new chain. These lessons were learned bitterly during the bear market of 2022; allowing us to innovate upon the reiteration of Konra when launching on DogeChain.

**Improvements include:**

* <mark style="color:blue;">Total Supply, all minted at once</mark>

The Total Supply of Konra was minted at once, with no ability to mint more as was the case in the beginning on SmartBCH. We learned the hard way, no matter how benign the idea of slowly minting the supply, the practice was time consuming and confused investors too much. So we settled on a final supply of 7777 tokens and minted them all at once.

* <mark style="color:blue;">**Token Lockers are our best Friend:**</mark>

Through deployment of Narath on SmartBCH we learned that token lockers are our best friend for controlling a supply that's not all needed at once. We applied this on DogeChain and immediately locked all initial liquidity and put a good part of the initial supply not used for Liquidity and community growing into time locks. See the basic information and Tokenomics section for more info. Time Locks earn reflections, so over time more and more Konra is out of circulation until the locks mature.

* <mark style="color:blue;">**Reflections instead of AutoStake program:**</mark>

We learned that maintaining an auto stake program which has to be done manually is a lot of work and it's not governed by Smart Contracts enough and thus prone to human error and delays. Instead we opted for a generous 5% holder's reflection. Thus Konra became a taxed token on DogeChain.

* <mark style="color:blue;">**Konra Recycling:**</mark>

Running out of Konra at key critical moments isn't fun and stagnates the project, as such the Konra Recycling was made automatic by a 3% DEV allocation of Konra from the Tax. These are recycled, which means once they are in the DEV address they are used for community building, creating extra trading pairs, farm rewards, as Merit for community members and whatever else is needed.&#x20;

This Recycling assures a steady supply of Konra finds it's way back to the project and gets reissued over and over again. We can use this in addition to any Konra paid by community members for future resources and services. See <mark style="color:blue;background-color:yellow;">Konra Recycling</mark> for more info (Coming Soon).

* <mark style="color:blue;">**Better LP Management:**</mark>

LP's were an issue on SmartBCH, I had made a critical error and only added a few hundred Konra into the initial liquidity pools. As such I always was playing catch up to try to build Liquidity. It cost me much from my personal funds and even till today liquidity is still on the low side.&#x20;

On DogeChain this is solved by two ways, a 2% allocation of the tax into Liquidity as well as setting larger initial liquidity pairs on multiple DEXs. This helped considerably, as much more of the supply is in liquidity on DogeChain with less hassle.&#x20;

Time locks keep this secure and over time once we find stable DEX's and DogeChain potentially moves to ZkEVM more liqudity will be burned and / or locked up for years at a time.

*<mark style="color:blue;">Konra on DogeChain became so well managed and set up tokenomics wise that it became the main instance of Konra and the token deployment on SmartBCH became a sub instance in the grand scheme of things. I'll explain that better in a future section of this White paper.</mark>*


---

# 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://konra-project.gitbook.io/konra-dogechain/konra-2.0.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.