Core formula
For a protected amountA, entry price E, expiry settlement price P, risk premium R, and maximum payout cap C:
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.
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.