> 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/resources/faqs.md).

# FAQs

Answers to common questions about KPK-curated vaults and pools, covering fees, how configuration changes are governed, review cadence, security monitoring, due diligence, and integration.

This section provides detailed answers to a range of common questions relating to KPK-curated products.

<details>

<summary><strong>How do fees on KPK-curated products work?</strong></summary>

Some protocols allow curators to charge fees. Where KPK applies such fees, they’re clearly stated on both the protocol’s interface and the relevant product page in this handbook. The exact mechanism depends on the underlying protocol.

For example, depositors in KPK's Gearbox pools pay no fees; the interest fee (20%, or 10% on some Credit Managers) is charged to borrowers on top of the interest they pay, so depositors receive the full borrow interest. Unless otherwise stated, curator fees (when applicable) are taken as a share of earned interest and are handled automatically within the product’s smart contracts.

</details>

<details>

<summary><strong>How are changes to KPK-curated products managed?</strong></summary>

All configuration changes are executed through **KPK’s multi-signature wallets,** following strict, auditable governance procedures. Because configuration updates are a key security vector, these changes are often subject to **timelocks** and predefined permissions to ensure transparency and control.

Most protocols we work with already implement **role-based restrictions** such as timelocks for sensitive functions and layered permission systems. On top of these, **KPK applies its proprietary** [**Permissions Layer**](https://kpk.io/blog/permissions-layer), which tightly scopes the actions curator multisigs can perform. This added layer ensures that only pre-approved transactions within well-defined parameters can be executed, significantly reducing the attack surface.

All changes are publicly visible onchain and recorded, with their transactions, in the [Change log](https://docs.kpk.io/changelog).

</details>

<details>

<summary><strong>How often are KPK-curated products reviewed and updated?</strong></summary>

Before launch, each product undergoes a thorough due diligence process. Once live, products and their underlying assets are continuously monitored, with **risk alerts tracked in real time and daily reviews** to assess anomalies or market changes.

Performance is reviewed on a **daily and weekly basis** to spot gaps or opportunities. High-level parameters such as liquidation thresholds or oracle configurations are typically stable and rarely adjusted more than once a month. Lower-level settings, like individual market allocations, may change more frequently in response to market dynamics. KPK can act within seconds when conditions require, **combining predictability for users** with **responsiveness to risk.**

</details>

<details>

<summary><strong>What security monitoring is in place?</strong></summary>

KPK combines **automated alerts, protocol-level monitors, and manual oversight** to protect curated products.

Every collateral and vault is covered by a bespoke set of monitors, including oracle liveness checks, price deviation alerts, governance proposal tracking, contract upgrade detection, and insolvency monitoring. We use third-party services such as **Hypernative** alongside in-house systems to ensure broad coverage.

For our Gearbox markets, an *Insolvency Monitor* continuously checks whether discounted collateral values exceed outstanding debt. If thresholds are breached, borrowing can be paused within seconds through the Emergency Admin role. Similar frameworks are applied across other integrated protocols.

</details>

<details>

<summary><strong>What due diligence does KPK perform?</strong></summary>

Before an asset or strategy is included in a curated product, KPK applies a structured [Curation Risk Framework](/vaults/infrastructure/risk-framework.md) that evaluates smart contract design, governance, oracle structure, liquidity, and broader market behaviour. This combines onchain and offchain analysis with external risk signals from platforms such as Credora, Exponential, and Pharos Watch.

The process continues after inclusion through ongoing monitoring, ensuring any material changes in risk are detected and addressed promptly. For more information, see the [Curation Risk Framework](/vaults/infrastructure/risk-framework.md).

</details>

<details>

<summary><strong>Do you provide direct access to KPK-curated products?</strong></summary>

Yes. KPK-curated vaults can be accessed through the [KPK app](https://app.kpk.io), and also through the user interfaces of the underlying protocols, such as the Morpho app.

Be cautious of any third-party sites claiming to offer direct access to KPK-curated products.

</details>

<details>

<summary><strong>How can my organisation integrate with KPK’s products?</strong></summary>

All KPK-curated products are permissionless: **integrators can interact directly through the protocols’ interfaces or smart contracts.**

For partners, KPK can design and deploy **custom lending markets or vaults**, helping protocols scale liquidity, broaden collateral coverage, or launch specialised strategies. To explore partnership opportunities, reach out via the [contact form](https://kpk.io/contact/) on our website.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kpk.io/vaults/resources/faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.