# Risk Controls

### Risk framework

hBTC is designed to operate within a **pre-defined, rules-based risk framework**. Risk management is automated and parameter-driven; the protocol does not rely on discretionary trading decisions. All risk controls are observable, threshold-based, and enforced through systematic mechanisms.

The primary risk control domains are **leverage**, **delta exposure**, and **interest spreads**, supported by a dedicated **reserve fund**.

<figure><img src="/files/sM2pjtajWqBrZMPZShBx" alt=""><figcaption></figcaption></figure>

#### 1) Leverage Control&#x20;

**Objective**\
Maintain a healthy money market position and reduce liquidation risk by operating within conservative Loan-to-Value (LTV) bounds.

**Current Thresholds**

* **Cap:** 51%
* **Target:** 50%
* **Floor:** 49%

**Mechanism**\
An automated off-chain service continuously monitors LTV and adjusts positions by opening or closing exposure when thresholds are breached, rebalancing toward the target.

{% hint style="info" %}

## Liquidation Parameters

**Zest protocol's** current liquidation parameters:

* **Liquidation threshold**:&#x20;
  * Paritial: 70% LTV
  * Full: 75% LTV
* **Liquidation penalty**: 5-10%
  {% endhint %}

{% hint style="warning" %}
If liquidation were to occur, the protocol may incur losses up to or exceeding the liquidation penalty, depending on market conditions and execution dynamics.\
\
\&#xNAN;*For additional details, see the* [*Market Risk disclosures*](/hbtc/risk-disclosures/market-risk.md)*.*
{% endhint %}

#### 2) Delta Control

**Objective**\
Maintain BTC exposure within a tightly defined delta-neutral range to minimize directional risk.

**Current Thresholds**

* **Cap:** 1.001
* **Target:** 1.0000
* **Floor:** 0.999

**Mechanism**\
When delta thresholds are breached, the protocol rebalances exposure via **Hermetica mint and redeem swaps** between stablecoins and sBTC, restoring exposure toward the target.

#### 3) Interest Spread Control

**Objective**\
Manage strategy exposure based on observed interest spread regimes, reducing or exiting positions when spreads become persistently unfavorable.&#x20;

**Current Thresholds**

* **Maximum negative spread:** 2 consecutive days of negative spread
* **Redeploy criteria:** 2 consecutive days of positive spread

**Mechanism**\
When negative spread threshold is breached, positions are closed or reduced. Strategy deployment resumes only after redeploy criteria are met.

#### 4) Reserve Fund

**Objective**\
Maintain a dedicated reserve fund that to buffer negative reward periods, subject to available capitalization.&#x20;

**Current Thresholds**

* **Reserve rate:** 5% of daily rewards
* **Minimum reserve capitalization:** 10 bps
* **Redeploy criteria:** 2 consecutive days of positive spread

**Mechanism**\
A defined portion of daily rewards (the reserve rate) is allocated to the reserve fund. If capitalization threshold is breached, positions are closed or reduced. Strategy deployment resumes only after redeploy criteria are met.

{% hint style="info" %}
The reserve fund is designed as a risk mitigation mechanism, **not as a guarantee against loss.**

*For additional details, see the* [*Reserve Fund documentation*](/hbtc/reserve-fund.md)*.*
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.hermetica.fi/hbtc/how-it-works/risk-controls.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.