> For the complete documentation index, see [llms.txt](https://docs.peapods.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peapods.finance/metavaults-lvf/insurance-fund-metavaults.md).

# Insurance Fund (Metavaults)

Peapods Metavaults are protected by an Insurance Fund, designed to provide a safety buffer in the event of unexpected losses or bad debt events.

#### Fund Size & Backing

* The Insurance Fund is backed by a minimum reserve of $200,000.
* These funds are reserved specifically for the purpose of risk mitigation across all active Metavaults.
* Governance (via vlPEAS votes) may choose to increase this minimum reserve threshold, but it can never be lowered below $200,000.

#### Purpose & Scope of Use

* The Insurance Fund is strictly limited to covering bad debt scenarios incurred by any Metavault.
* **Decision-Making Authority**:
  * Deployments from the Insurance Fund must be approved by either:
    * A vlPEAS governance vote, or
    * The Peapods Finance core team, if urgent action is required.

#### Limits of Protection

* The Insurance Fund is capped by its available balance.
* Once depleted, no further coverage is available until additional funds are allocated.
* The Insurance Fund does not guarantee against all losses, but instead provides a structured safety net to minimize systemic risk.

***

> **Disclaimer**\
> \&#xNAN;*The Insurance Fund should not be relied upon as a guarantee of repayment or full coverage for all participants. Users assume the edge-case risk that losses may exceed the available balance of the fund.*


---

# 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://docs.peapods.finance/metavaults-lvf/insurance-fund-metavaults.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.