LogoLogo
AddressesAuditsGitHub
  • 📥Introduction
  • 🌀Products
    • Introduction
    • Best Yield
      • Overview
      • Guides
        • Deposit funds on BY
        • Redeem funds on BY
      • FAQs
    • Yield Tranches
      • Overview
      • Adaptive Yield Split
      • Security
        • Covered risks
      • Guides
        • Deposit funds on YTs
        • Redeem funds on YTs
        • Live YTs guides
          • Lido stETH
      • FAQs
    • Fee structure
    • Get involved
      • Integrators program
      • Institutions program
  • 💻Developers
    • Introduction
    • Networks and codebase
      • Ethereum mainnet
      • Polygon
      • Kovan testnet
      • ERC-4626 standard
    • Best Yield
      • Architecture
      • Deployed contracts
        • Ethereum
        • Optimism
      • Interface
      • Methods
        • mintIdleToken
        • redeemIdleToken
        • redeemInterestBearingTokens
        • rebalance
        • tokenPrice
        • tokenPriceWithFee
        • getAPRs
        • getAvgApr
        • userAvgPrices
        • getGovTokensAmounts
        • getAllocations
        • getGovTokens
        • getAllAvailableTokens
        • getProtocolTokenToGov
      • Edge cases
      • Security management policy
      • Get integrated as yield source
      • Get user earnings
    • Yield Tranches
      • Architecture
      • Deployed contracts
        • Ethereum
        • Polygon zkEVM
        • Optimism
      • Interface
      • Methods
        • AAStaking
        • BBStaking
        • AATranche
        • BBTranche
        • depositAA
        • depositAARef
        • depositBB
        • depositBBRef
        • fee
        • getApr
        • getContractValue
        • getCurrentAARatio
        • getIncentiveTokens
        • lastNAVAA
        • lastNAVBB
        • strategy
        • strategyToken
        • token
        • trancheAPRSplitRatio
        • tranchePrice
        • virtualPrice
        • withdrawAA
        • withdrawBB
      • Integration example
      • Edge cases
      • Security management policy
      • Subgraph
    • API
    • Security
      • Hats Finance vault
      • Hypernative monitoring
      • Immunefi bug bounty
      • Integration Standard Requirements
      • Risk Framework
      • Smart contract audits
  • 🏛️Governance
    • Introduction
    • Idle DAO
      • Governance process
        • Governance forum
        • Governance dashboard
        • Snapshot IDLE
        • Snapshot stkIDLE
      • Idle Leagues
        • Communication League
        • Development League
        • Treasury League
        • Leagues contributors
      • Treasury
        • Reports
      • Governance guides
        • How to monitor off-chain voting pools
        • How to propose an IIP
        • How to create an on-chain proposal
        • How to delegate votes
        • How to vote for an IIP
      • FAQs
    • IDLE token
      • Distribution
      • Use cases
        • Lending, borrowing & collateral
        • DEXs liquidity provision
      • Buybacks
      • Delegates
      • CoinGecko
    • IDLE staking
      • Prime staking
        • Examples
      • Staking integration
      • Guides
        • How to stake your IDLE
        • How to vote in Gauges
        • How to boost your $IDLE rewards
        • How to give VEV
  • 🗂️Other
    • Brand assets
    • Guides
      • How to see IDLE in your wallet
      • Deposit funds through Idle
      • Deposit funds through smart contracts
      • Redeem funds through Idle
      • Redeem funds through smart contracts
    • FAQs
    • Glossary
    • Resources
    • Archive
      • 👇Get in touch
        • 🏛️Governance Forum
        • 🏆Idle Grants Program
        • 👾Discord
        • 🐦Twitter
      • Gauges
        • Architecture
        • Deployed contracts
        • Gauges repository
        • stkIDLE repository
      • Gauges
        • Gauges integration
        • FAQs
      • Boost
      • DEXs liquidity provison
      • Risk Adjusted (deprecated)
      • Deployed contracts
      • Idle Smart Treasury (deprecated)
      • Ethereum LP staking (deprecated)
      • Polygon LP staking (deprecated)
      • Flash Loans (deprecated)
      • QuickSwap cxETH-WETH
      • Integrate PYTs
      • Idle Grants program
      • Idle on Polygon
        • Add Polygon network to MetaMask
        • Bridge $IDLE to Polygon
        • Deposit funds on Polygon
        • Add liquidity to $IDLE pools
        • Stake IDLE LP tokens on Polygon
Powered by GitBook

Ecosystem

  • Website
  • App
  • Governance
  • Brand assets

Developers

  • Feedback
  • GitHub
  • Bug bounty
  • Audits

Community

  • Blog
  • Twitter
  • Telegram
  • Discord

Analytics

  • Stats
  • Dune
  • DeFiLlama
  • CoinGecko
On this page
  • Automated Market Makers
  • Lending Protocols
  • Liquid staking protocols
  • Leveraged strategies
  • Options strategies

Was this helpful?

  1. Products
  2. Yield Tranches
  3. Security

Covered risks

Products > Yield Tranches > Covered risks

Last updated 1 year ago

Was this helpful?

Each Yield Tranche is based on one or more yield sources, which are exposed to a set of dependencies and risks. Additionally, every YT is subject to underlying strategy and risks.

Given the nature of the two classes of tranches, which differ in terms of risks and gains opportunities, it is possible to explain their behaviour through two scenarios: a Yield case and a Loss case. See Yield and Loss scenarios in the section.

In general, Senior YTs holders always benefit from the payout priority (first in line to redeem their funds) after events that can cause a decrease in:

  • the exchange rate between YTs-managed yield-bearing tokens' and the underlying asset

  • the exchange rate between YTs tokens and the underlying asset

Examples:

  • A downstream lending market suffers a loss of funds and the price of the yield-bearing tokens deployed by YTs decreases. The affected Junior and Senior YTs are automatically paused.

  • The YTs’ main contract, idleCDO, suffers a loss of funds, letting the attacker redeem deposited yield-bearing tokens. The price of the YT token decreases. The affected Junior and Senior YTs are manually paused.

YTs interact with a range of DeFi primitives, each with its own specific risks. Every primitive, though, share a number of common risks:

Risk
Description
Outcome
Coverage

Smart contract

Exploit of a bug in downstream yield protocols' code

Partial loss of funds

Yes

Governance

Adverse changes to protocol parameter

Partial loss of funds

Yes

Asset de-peg

The peg of a token against another asset is lost

Reduced value against other units of account

No

A list of specific risks affecting Automated Market Makers, Lending protocols, Liquid Staking protocols, Leveraged strategies and Options strategies follows.

Automated Market Makers

Risk
Description
Outcome
Coverage

Impermanent loss

Change of the token price in the underlying pool

Reduced fiat ($) value

No

Lending Protocols

Lending protocols are mainly classified into two categories based on the type of loans they offer: overcollateralized and undercollateralized.

Overcollateralized lending

Risk
Description
Outcome
Coverage

Incorrect price feed

Oracle manipulation or failure

Bad debt creation

Yes

Unappropiate collateral factors

Generation of untenable positions

Bad debt creation

Yes

Wrong liquidation

Liquidation does not work as expected

Bad debt creation

Yes

Undercollateralized lending

Risk
Description
Outcome
Coverage

Borrower default

Borrower is not able to pay back the loan and is insolvent

Partial loss of funds

Yes

Liquid staking protocols

Risk
Description
Outcome
Coverage

Validator key management

Loss of multisig keys holding staked ETH

Partial loss of funds

Yes

Slashing

Staking penalties for validators' network

Partial loss of funds

Yes

NB - YTs do not cover Senior LPs funds in case of events leading to a de-peg.

Leveraged strategies

Risk
Description
Outcome
Coverage

Liquidation

Liquidation of the position at loss

Partial loss of funds

Yes

Instadapp Yield Tranches

Instadapp lite vaults have automation functions, which automatically rebalance the vault during market changes. If the vault gets risky, it can first refinance into another protocol to maintain safety or deleverage by selling stETH and paying back the ETH debt. This kind of automation, if required or occurs, may incur losses caused by trading slippage:

  • If the loss is less than or equal to 0.5%, the loss will be distributed proportionally among the funds deposited in the tranches. This usually occurs when the borrowing rate of WETH is higher than the lending rate of stETH.

  • If the loss is between 0.5 and 5%, the Junior tranche will absorb the entire loss and the tranche will continue to work as usual.

  • If the loss is greater than 5%, the automating pausing of the Tranche is triggered. Deposits and redeems are halted.

Options strategies

Risk
Description
Outcome
Coverage

Financial

The strategy generates negative returns

Partial loss of funds

Yes

🌀
Overview
Idle YTs infrastructure