FAQs
Products > Perpetual Yield Tranches > FAQs
Read the PYTs Edge Cases section to learn more about default or hack scenarios and how they would be managed.
If a protocol is hacked wouldn't its underlying token be useless? How does Junior create value after an exploit?
If the attacker is able to completely drain a protocol, both Senior and Junior tranches would be affected. This event is extremely rare, as usually a hack is composed of recursive interactions that steal part of the funds. When the protocol itself is hacked, there are guardians that can pause the system and prevent further losses. Even if validators are directly hacked, it's unlikely that all the validators will suffer the same issue, just causing partial losses.
In this vision, Senior Tranche increases the security profile of the liquidity provider, adding an extra layer of protection: Junior Tranche deposits.
PYTs would follow the Clearpool default process (insurance, auction) and then redistribute $USDC reimbursed to the Tranches token holders.
There can be 2 scenarios:
- Senior tranche is fully covered and Junior tranche redeems a portion of deposited assets: Senior LPs withdraw their entire deposit; Junior LPs will proportionally redeem their funds using a redistribution contract.
- Senior tranche redeems a portion of deposited assets and no liquidity is left on Junior tranche: Senior LPs will proportionally redeem their funds using a redistribution contract.
In the case of borrower default on Clearpool, where the NAV does not decrease, the pausing process will be the following:
- on Clearpool itself, you cannot redeem because utilization rate is 100% and the pool is locked until auction.
- the PYTs is manually paused, but the underlying is already locked.
- once the USDC refund is processed by Clearpool, PYTs are unpaused (according to the 2 scenarios described above).
There are no locking periods or epochs and users are free to enter and exit at any time. The interest earned (and governance tokens, after being partially sold in the market) will be split between the two classes using the Adaptive Yield split.
The base APY, before being split between tranches, is provided by the underlying strategy that takes into account the reinvestment of the accrued governance tokens (except for eventual IDLE rewards). The actual APY of each tranche class is determined by the ratio between the current underlying TVL of Senior and Junior tranches (i.e. APY = share of yield allocated to senior tranches/Senior TVL). The APY has to be considered net of fees.
Fees are collected at each harvest event. When the strategy auto-reinvest accrued tokens, the Idle protocol charges a 10-15% performance fee (see the Fee structure section).
Last modified 3mo ago