> 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-mechanics.md).

# Risk Mechanics

Failure towards levelling dNFTs is associated with two primary risks: ‘downgrade risk’ & ‘breakage risk’. Any unsuccessful upgrade attempt bears a 30% likelihood for the dNFT to revert to its preceding level. Further accentuating these stakes, there’s a further 20% risk that the dNFT might break, leading to total compromisation of the asset. 

However, Levels 3, 6, and 8 are distinctly characterized as ‘safety levels’. Serving as buffers within the dNFT levelling mechanics, these safety levels provide dNFTs with immunity from the aforementioned downgrade and breakage risks. They act as safety havens, allowing for more deliberate and considered progressions through the dNFT levels.

These intricate risk mechanics compels dNFT holders to exercise discernment and strategy in their dNFT levelling pursuits. The need for added protective measures thus emerges - introducing risk protection mechanics, designed to insulate dNFTs from the inherent downgrade and breakage risks associated with levelling failures.

<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, and the optional `goal` query parameter:

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