> For the complete documentation index, see [llms.txt](https://whitepaper.nuon.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.nuon.fi/architecture/emergency-mode.md).

# Emergency Mode

When the protocol reaches a critical state of having no buffer, it is at risk of approaching undercollateralization and being unable to process redemptions. If the collateral ratio is less than 100% (time averaged over 1 week, 3 days and 24 hours) then Emergency Mode is activated. To remedy this, the protocol goes into a status in which all vaults are liquidated for USDC which is done via a Dutch auction process. During this process minting and redeeming is disabled. Once all USDC has been acquired from winding down the vaults, NUON is redeemable at a pro rata value.

Individual vaults can also be closed if the vault is underperforming. This is determined as the vault having <90% value compared to the amount of USDC input into the vault. The vault must also have a return that is less than the average return rate for all vaults. If both conditions are met, then the vault begins a wind down with its assets being sold for USDC in a Dutch auction and placed into the buffer.


---

# 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://whitepaper.nuon.fi/architecture/emergency-mode.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.