Skip to main content
The CoverFi economics model is designed around visible fees, capped payout exposure, and reserve capacity accounting.

Core formula

For a protected amount A, entry price E, expiry settlement price P, risk premium R, and maximum payout cap C:
Example:

Reserve capacity and position-specific payouts

Every active position locks the maximum payout amount from available reserve capacity. This prevents the app from accepting more exposure than the reserve can support.
When a position settles with no payout, unused locked capacity is released. When a position settles with a payout, the full calculated payout is reserved for that position and the owner can claim it through the engine. Current V2 routing: The protocol portion is transferred automatically to the configured treasury address during position creation. Approved partner rewards, when present, are paid from the protocol portion before the remaining protocol amount reaches treasury. Reserve-provider withdrawals use shares, NAV, a cooldown queue, and available-liquidity checks. Locked liabilities, reserved claims, unearned premiums, safety funds, and automation funds are excluded.

Example claim timeline

Premium policy

Premiums are non-refundable after a signed position is accepted. They compensate reserve liquidity providers and increase protocol reserves depending on deployment configuration. Current product premium schedule: Premium pricing should account for:
  • Asset volatility and historical depeg frequency.
  • Duration.
  • Entry price captured from the oracle at position creation.
  • Current reserve utilization.
  • Maximum payout cap.
  • Oracle confidence and feed freshness.

Risk controls

The model should not go to production without:
  • Per-asset exposure limits.
  • Maximum position size per wallet.
  • Reserve utilization caps.
  • Oracle freshness checks.
  • Settlement, payout-claim, and principal-withdrawal monitoring.
  • Emergency pause procedures.
  • Published fee and payout examples.

What this is not

CoverFi protection is not insurance, does not guarantee payout, and is not a promise that a user will be made whole. It is a smart-contract-based protection mechanism constrained by contract rules, reserve funding, oracle data, and network execution.