> 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/chain-fail-safe.md).

# Chain Fail - Safe

DRAFT:

The Project has a unique idea for the unlikely event that a blockchain where an instance of Konra is deployed fails completely or there is another horrible effect that impacts a lot of users in our community. 

A part of the supply will be set aside in reserves to cover those community members who:

* Hold Konra on another chain, to be allocated ONLY if the chain fails or goes stagnant to the point we have to move.
* Lose their Konra through an action that they, nor we could have foreseen that affects a large amount of investors at once (ie major rug pull, major bridging or wallet or blockchain exploit, dex shutting down losing them access to farms / ranches or loss of a staking platform). 

We learned from the events of SmartBCH and the collapse of multiple big projects in 2022 that chains can fail and sometimes do fail. We've also lost access to LPs and farms from DEXs that went under, had community members lose a large amount of their holdings through a rug pull of a staking platform in 2023. 

As such, we find it prudent from beginning of 2023 to create reserves for just such events to cover Konra holders in case their parent blockchain collapses or other horrible things happen.

* These reserves were still waiting to be locked up in a time lock when they needed to be used in 2023 to recoup Community members who lost their holdings in the Swamp rug pull. Upon recovery we will rebuild the reserves in case we need them again in the future.

This reserves is in Konra and may include other tokens of our ecosystem IF needed in worst case. At first it will be fractional, but as time goes on and we deploy more resources on various blockchains these reserves will be fully backed; as the reserve pools of 2 or more functional chains can cover one that fails.....

Address where Reserves will be held on DogeChain:

Still at the DEV address for now as it's needing to be used. We will build new reserves in the new year.

Initial Allocation to reserves:

400 Konra:

Dec 2023 - Feb 2024, currently being used to cover community members who lost their Konra in the Swamp rug pull. We will have to rebuild these reserves before we can deploy them again in the future.

How to increase this reserve pool:

Reflections will increase the pool naturally and we may choose to add some of the recycled Konra into the reserves pool as time goes on.

<mark style="color:green;">Who would be covered:</mark>

<mark style="color:green;">Anyone impacted in these ways when a chain goes down:</mark>

* <mark style="color:green;">Those who held the Konra in their wallets</mark>
* <mark style="color:green;">Those who held LP tokens in their wallets</mark>
* <mark style="color:green;">Those who had proof that they staked or farmed their tokens</mark>&#x20;

<mark style="color:green;">Anyone impacted in these ways when a major rug pull or loss of funds occurs:</mark>

* <mark style="color:green;">Those who used a farming or staking platform and lost their tokens</mark>
* <mark style="color:green;">Other instances as determined by the team</mark>

<mark style="color:orange;">Who would not be covered:</mark>

We will always try to do an thorough investigation to try to get all of the holders restored, but nothing is perfect. In the cases below we may not get everyone restored as we may not have enough information or the tokens in these cases aren't covered.

* <mark style="color:orange;">Anyone where we could not prove they held the tokens</mark>&#x20;
* <mark style="color:orange;">Anyone who bought or staked or moved their tokens to close to the event and we can't determine as some instances records are affected.</mark>
* <mark style="color:orange;">Tokens held in Liquidity pools by Project</mark>
* <mark style="color:orange;">Tokens held in token locks, by project Devs</mark>
* <mark style="color:orange;">Tokens in farm rewarders that weren't harvested</mark>
* <mark style="color:orange;">Any event that does not impact a large amount of holders</mark>
* <mark style="color:orange;">Normal outages as are common for blockchains</mark>
* <mark style="color:orange;">Smaller, less impactful rug pulls</mark>
* <mark style="color:orange;">Impact of sales on the chart that's a normal part of crypto</mark>

How we could do this:

We would encourage holders with large farming pools to make screen shots and take other proof of farming activity and staking activity. If the blockchain explorer remains intact after a chain collapses or another incident we'd use the information on there & wallet records to piece together holders information after a collapse / incident as best as we can.


---

# 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/chain-fail-safe.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.