Overview

This section provides an overview of the protocol.

Roles

  • Token holders vote for risk policies, curators, and guardians
  • Risk curators set up pools. They can underwrite pools ("self stake") and set commissions on yield (risk metrics). They can also restrict pool access via gate contracts
  • Underwriters vote for up to 5 pools they want to underwrite with yield-bearing tokens plus backup direct investment
  • Users receive yield-bearing iX tokens with fast exit capability into any asset of the pool
  • Underwriters receive yield-bearing uX tokens with 28-day unlock period and liquidity-dependent exit
  • Guardians are AI systems that monitor positions and close them if policies are violated or insurance pools become undercapitalized

Insurance Process

1

Deposit

  • Underwriters deposit yield-bearing stablecoin X to insure a pool and receive underwriter receipt token uX
  • Users deposit yield-bearing stablecoin Y. This is only possible if there is sufficient X in the pool. The deposit of Y initiates the lock for X; as long as there is no Y, underwriters can immediately withdraw their deposits
2

Being Insured

  • Over time, X and Y increase in value due to underlying yield. X receives a small amount of Y tokens (Cy) that can only be claimed by X holders
3

Withdraw

1

All Good

  • Users deposit their iY tokens and receive payment in Y
  • Underwriters deposit their uX tokens and receive payment in X after 28 days
2

Problem with Y

  • Users deposit their iY tokens and receive payment in X
  • Underwriters deposit their uX tokens and request payment in X, but must wait 28 days. However, there may be nothing left once the request is executed. Underwriters can only request payment in Y if X is already depleted. Next, underwriters would request what remains in the pool, and Y might still retain some value
3

Problem with X

  • Users deposit their iY tokens and receive payment in Y
  • Underwriters deposit their uX tokens and request payment in X, but must wait 28 days. However, there may be nothing left once the request is executed