> For the complete documentation index, see [llms.txt](https://docs.kpk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpk.io/vaults/infrastructure/coverage.md).

# Coverage

[KPK's curated vaults](https://opencover.com/vaults/kpk) offer discretionary cover so that depositors can hold a covered position that responds to certain technical and economic loss events. Cover is an optional, vault-level feature: it does not change how a vault is curated, allocated, or monitored, and it sits alongside the controls described in the Risk framework.

The cover is provided through a partnership between [Nexus Mutual](https://nexusmutual.io/) and [OpenCover](https://opencover.com/). KPK arranges and maintains the cover for its vaults. Three parties are involved, with distinct roles.

<table><thead><tr><th width="160" valign="top">Party</th><th>Role</th></tr></thead><tbody><tr><td valign="top"><strong>Nexus Mutual</strong></td><td>Underwriter and risk carrier. Provides the discretionary mutual cover that stands behind the covered position, and assesses and decides claims under its cover terms.</td></tr><tr><td valign="top"><strong>OpenCover</strong></td><td>Distributor and broker. Builds and operates the Covered Vault contracts through which the cover is arranged, priced, and maintained. OpenCover distributes Nexus Mutual cover; it is not the risk carrier.</td></tr><tr><td valign="top"><strong>KPK</strong></td><td>Curator. Has arranged cover for its vaults. KPK is not the provider, does not bear the risk, and does not guarantee any payout.</td></tr></tbody></table>

The Covered Vault contracts are built on tokenised-vault standards and have completed independent security audits (Nethermind and Sherlock). For the contract-level detail, see the [OpenCover documentation](https://opencover.com/).

### How the cover works

OpenCover's Covered Vaults wrap a vault position with cover at the contract level, so a depositor activates cover by depositing rather than by arranging cover separately.

{% stepper %}
{% step %}
**Covered Vault wrapper**

A depositor enters through an OpenCover Covered Vault, a contract that wraps the underlying KPK-curated vault. The depositor keeps the same underlying exposure, strategy, and yield as the uncovered vault.
{% endstep %}

{% step %}
**Cover activation**

Cover is activated by depositing into the Covered Vault, without leaving the vault interface or arranging cover separately. Exiting the Covered Vault ends the cover on that position.
{% endstep %}

{% step %}
**Premium streaming**

The premium streams continuously from the position's yield, with automatic renewal and no minimum term. The depositor pays only for the duration of the cover held.
{% endstep %}
{% endstepper %}

For Covered Vaults, OpenCover administers the cover programmatically as the Covered Vault Manager, so depositors are not required to file claims individually. Claims are reviewed by Nexus Mutual's Claims Committee following a cool-down period.

### Scope

Cover responds to specific technical and economic loss events affecting the covered position, as defined in the Protocol Cover terms. The cover responds to a loss of funds caused by any of the following, as defined in the cover wording:

<table><thead><tr><th width="200" valign="top">Event</th><th width="544.52734375">Description</th></tr></thead><tbody><tr><td valign="top"><strong>Smart contract exploits</strong></td><td>A code bug or error that causes the designated protocol to be used in an unintended way.</td></tr><tr><td valign="top"><strong>Oracle failure</strong></td><td>Incorrect price-feed data used by the protocol's contracts, where the error exceeds 1% for stablecoin-related oracles or 2.5% for other assets, arising from faulty configuration, missing safeguards against unauthorised updates, or feeds that fail to update.</td></tr><tr><td valign="top"><strong>Oracle manipulation</strong></td><td>Price-feed data that is deliberately corrupted and leads to a loss of funds.</td></tr><tr><td valign="top"><strong>Liquidation failure</strong></td><td>Keepers cannot liquidate collateral backing unhealthy borrow positions, resulting in bad debt socialised across lenders in the affected market, or they liquidate that collateral for less than 80% of fair realisable market value.</td></tr><tr><td valign="top"><strong>Governance takeovers</strong></td><td>A malicious actor forces through a malicious upgrade to a designated protocol contract.</td></tr></tbody></table>

Covered Vaults do not cover all losses, and they do not eliminate risk. Market movements, yield variation, and other events outside the cover wording are not covered, and the cover is subject to exclusions and a deductible.


---

# 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.kpk.io/vaults/infrastructure/coverage.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.