> For the complete documentation index, see [llms.txt](https://bliv.gitbook.io/bliv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bliv.gitbook.io/bliv/bliv-dnfts/nft-mechanics/risk-protection.md).

# Risk Protection

To mitigate the risks of downgrading or breakage during dNFT levelling, protection mechanisms can be activated to bolster the resilience of dNFTs against these risks associated with levelling failures. This allows dNFT holders to pursue dNFT levelling with greater assurance and reduced apprehension upon the risk mechanics involved.

The significance of the risk protection mechanics becomes most evident when dNFTs are situated at upper echelons. As dNFTs ascend to higher levels, the inherent odds of a successful upgrade become remarkably slim. This positions the risk protection mechanics as an invaluable asset, acting as a safety net against the fallout of dNFT levelling setbacks.

To enable risk protection, an allocation of a specific amount of LiV (contingent upon the dNFT’s level) will be required. This LiV costing serves a dual purpose: it fortifies dNFTs against the risks mechanics associated with levelling failures, whilst accentuates the intrinsic utility and value of LiV within the larger BLiV ecosystem.

<br>


---

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

```
GET https://bliv.gitbook.io/bliv/bliv-dnfts/nft-mechanics/risk-protection.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.