88mph Docs v4
  • Introduction
  • Disclaimer
  • Getting started
    • Fixed yield rate
    • Yield tokens
    • Risk mitigation
  • MPH, veMPH and Gauges
    • MPH Tokenomics
    • veMPH
      • Understanding veMPH
      • Using veMPH
    • Gauges
  • Developer docs
    • Integration guide
    • Smart contract architecture
    • Smart contract references
      • DInterest
      • DInterestLens
      • ZeroCouponBond
    • Deployment guide
    • Audits / Security
    • Smart contract addresses
    • REST API
    • Ethereum subgraph
    • Ethereum Rinkeby subgraph
    • Fantom subgraph
    • Avalanche subgraph
    • Polygon subgraph
  • Governance
  • Governance
    • Proposals
  • Forum
  • Vote
  • Governance guidelines
  • Governance treasury
  • Grants & Funding
  • Resources
    • Docs v3
    • Docs v2
  • Changelog
Powered by GitBook
On this page
  • Fixed yield rate oracle
  • Yield surplus
  • Yield balancing
  1. Getting started

Risk mitigation

PreviousYield tokensNextMPH Tokenomics

Last updated 2 years ago

The main risk of depositing funds into 88mph is the risk of insolvency, the situation where 88mph does not have enough funds to return the deposited funds plus fixed yield to a user.

88mph and CADLabs have worked together to create a radCAD agent-based model to simulate liquidity and network revenue dynamics for the 88mph v3 protocol. To understand how 88mph model works to mitigate those risks, we invite our users to read the using radCAD pubished by CADLabs.

88mph is a new protocol, but has undergone multiple .

TL;DR

88mph relies on three lines of defense to mitigate the risk of insolvency (listed in order of which gets rekt first):

  1. An that can accurately price (not necessarily predict) future yield. This ensures that get sold most of the time.

  2. Frequent , which allow 88mph depositors to accumulate the forfeited yield to build up a surplus that acts as a backstop.

  3. Volatile floating yield rates in the underlying yield protocols, which allows 88mph to use the surplus yield from deposits that were offered low fixed yield rates to subsidize the deficit caused by the deposits that were offered high fixed yield rates.

Fixed yield rate oracle

For the first line of defense, building oracles for pricing future yield is quite difficult, since there is not a lot of prior work on the matter. Realistically speaking, 88mph will probably settle with building an oracle that offers a rate lower than the market rate most of the time, which trades efficiency for security.

Yield surplus

For the second line of defense, integrating with other protocols, specifically vaults a la Yearn, will likely help a lot. Vaults generally have frequent deposits & withdrawals, and whenever an early withdrawal happens, not only is the forfeited yield used for 88mph's risk mitigation, an early withdrawal fee is also taken. Using MPH incentives to get vault protocols on board will probably be worth it.

Yield balancing

For the third line of defense, there's not much we could do about it. Vault integrations will likely help a bit though, since frequent deposits & withdrawals mean there will be diversity in the fixed yield rates offered to deposits, giving the balancing act more to work with.

analysis of 88mph protocol dynamics
security audits
yield tokens
oracle
early withdrawals