# 7.2 Operational Risk Controls

#### Operator Default Protocol

*Figure 7.C — Default Waterfall*

<table data-header-hidden><thead><tr><th width="152.99993896484375"></th><th width="193.88885498046875"></th><th width="262.3333740234375"></th><th width="135.444580078125"></th></tr></thead><tbody><tr><td>Stage</td><td>Trigger</td><td>Action</td><td>Timeline</td></tr><tr><td>1. Warning</td><td>LTV breach</td><td>24-hour cure period; additional collateral required</td><td>T+0 ~ T+24h</td></tr><tr><td>2. Liquidation</td><td>Cure period expires</td><td>Automatic collateral liquidation</td><td>T+24h</td></tr><tr><td>3. Insurance</td><td>Collateral shortfall</td><td>Insurance fund deployed</td><td>T+24h–T+48h</td></tr><tr><td>4. Mutualization</td><td>Insurance insufficient</td><td>Loss distributed across Vault</td><td>T+48h+</td></tr></tbody></table>

#### Insurance Fund

Funded by **5% of protocol fees**, targeting **3% of Vault TVL**.

* Automatic deployment for losses below $500,000
* Losses above threshold require DAO approval
* Fully auditable on-chain

*Figure 7.D — Insurance Fund Sizing*

<table data-header-hidden><thead><tr><th width="106.888916015625"></th><th width="120.8887939453125"></th><th width="173.22235107421875"></th><th width="195.5556640625"></th><th width="151.44427490234375"></th></tr></thead><tbody><tr><td>Scenario</td><td>Default Rate</td><td>Loss Given Default</td><td>Annual Loss (on $25M TVL)</td><td>Required Fund (2x buffer)</td></tr><tr><td>Optimistic</td><td>2%</td><td>15%</td><td>$75K</td><td>$150K</td></tr><tr><td>Base Case</td><td>5%</td><td>25%</td><td>$312.5K</td><td>$625K</td></tr><tr><td>Stress</td><td>10%</td><td>40%</td><td>$1.0M</td><td>$2.0M</td></tr><tr><td>Severe</td><td>15%</td><td>50%</td><td>$1.875M</td><td>$3.75M</td></tr></tbody></table>

*Assumes 150% overcollateralization. Loss Given Default represents residual loss after collateral liquidation.*

#### Concentration Controls

* Maximum 10% node share per operator (enforced via registry)
* Minimum 3 geographic regions per operator
* Incentives for small operators (<10 nodes) via fee subsidies
* Governance cap: maximum 3% voting weight per address
* Target Nakamoto coefficient ≥ 8; governance intervention triggered if breached

#### Smart Contract Security

* Formal verification prior to mainnet (Certora or equivalent)
* Two Tier-1 independent audits (target: Trail of Bits + OpenZeppelin)
* 48-hour timelock on all upgrades
* Immunefi bug bounty program up to $500,000

#### SLA Enforcement

*Figure 7.E — SLA Penalty Schedule*

<table data-header-hidden><thead><tr><th width="159.22222900390625"></th><th width="213.66668701171875"></th><th width="349.555419921875"></th></tr></thead><tbody><tr><td>Uptime</td><td>Penalty</td><td>Outcome</td></tr><tr><td>≥99.5%</td><td>None</td><td>Full revenue allocation; normal operation</td></tr><tr><td>99.0–99.5%</td><td>10% revenue reduction</td><td>Warning; 30-day cure period</td></tr><tr><td>97.0–99.0%</td><td>25% reduction</td><td>Allocation restrictions; review</td></tr><tr><td>95.0–97.0%</td><td>50% reduction</td><td>Suspension; remediation plan required</td></tr><tr><td>&#x3C;95.0%</td><td>Collateral slashing</td><td>Deregistration initiated</td></tr></tbody></table>


---

# 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://railquant.gitbook.io/quantarail/7.2-operational-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.