Authors: banteg, flashfish, jiji, jmonteer, newmickymousse, saltyfacu, wavey
Establish a new yTeam, yRates, and transfer to it the “Set Fees” power, with the requirement that earned fees must never exceed the yield earned by vault depositors.
This proposal is currently in the discussion phase. As per our voting rules outlined in YIP-55, it will be in discussion for at least 3 days with a non-binding forum poll to gauge sentiment before it can be assigned a YIP number and move to Snapshot for a binding vote.
In the previous bull market, opportunities were readily available, and Yearn vaults could generate high yields. Since the height of DeFi Summer those yields have shrunk, and it is now common for many crypto assets to return in the lower single-digit APRs.
Yearn vaults never deploy funds unless vault depositors profit from this, as this would add unnecessary risk to depositor funds.
In current low APR environments, this rule forces Yearn vaults to have large amounts of capital uninvested, earning no income for depositors or the Yearn treasury.
As per YIP-51, the current fee structure is:
- 2% management fee
- 20% performance fee
Fees are automatically levied on deployed capital only, and is the primary income source for the Yearn treasury. It finances protocol expenses including grants, gas costs, infrastructure, YFI buybacks, and more.
If a vault strategy is earning 2.5% APR or less, depositors stand to realize no profit on harvest (after the current mgmt + performance fees), which means that funds do not get deployed to this strategy. In such a scenario, some of the implications are that:
- All strategies which earn between 0.5% - 2.5% APR become non-viable.
- Yearn treasury earns no fees.
- Yearn vaults require additional monitoring to react to situations where APR dips too low capital needs to be unallocated.
As per YIP-61, yTeams…
…are small, autonomous groups of yearn contributors empowered by YFI holders to act independently in the best interest of Yearn within a constrained domain of action and with enumerated, discrete decision-making powers.
Examples of existing yTeams are yBudget, yOps, and yPeople, each having their own distinct domain and decision-making powers.
“Set Fees” power is currently with YFI holders, as per YIP-61.
YFI holders have the power to ratify new yTeams.
The yOps team has the power to ratify new signers for yTeams.
Efforts are underway to evolve protocol operations across several areas to improve performance during the bear market. As part of this, a dedicated team that is responsible for product fee structures and can react on short notice will allow vaults to stay competitive with higher yields that draw more TVL.
This benefits all stakeholders: vault depositors earn more yield, yearn treasury accrues more fees, and YFI holders see more capital allocated for YFI buybacks.
By establishing strict fee guidelines, yTeam powers become better restricted. Vault depositors also get an understanding of the worst case impact of fees.
- A fee dashboard to visualize current fee structures across vaults to depositors and improve transparency.
- Delegation to veYFI lockers to dynamically adjust fees of vaults.
- Ratify a new yTeam, yRates. yOps is tasked with ratifying initial signers and quorum, but it must consist of at least four individual signers. This does not imply increasing full time grants, signers can be taken from the existing contributor pool.
- Transfer the “Set Fees” power to yRates from YFI holders.
- Enforce a strict condition that Yearn fees must never exceed the yield paid out to its vault depositors, instructing yRates team members in their work to optimize fees to benefit both vault depositors and the Yearn treasury.
- Moving forward, the published quarterly financial reports should include an update prepared by yRates on past fee structures performance and the future outlook. These updates should not block the publication of the report.
- Building during bera. Haven’t you heard, anon? DeFi is dead… | by banteg | Yearn | Jun, 2022 | Medium
- yearn-pm/financials/reports at master · yearn/yearn-pm · GitHub