This proposal seeks to gather input from vlMGP holders on whether Magpie should support the adjustments outlined in Penpie’s PIP #16.
Abstract
This proposal is the first in a series of planned adjustments aimed at improving the mPendle peg while optimizing the revenue mechanisms for Penpie’s VOTER and BASE streams. It introduces a temporary suspension of the CAKE LP establishment for VOTER revenue, addressing inefficiencies and potential impermanent loss, and proposes a new allocation strategy for BASE revenue to better support operational needs and incentivize liquidity pools. These changes are designed to enhance resource utilization, stabilize the ecosystem, and position Penpie for future growth. For additional context about Pendle’s vePENDLE revenue model: Pendle Docs.
Motivation
This proposal introduces adjustments aimed at addressing inefficiencies in Penpie’s revenue mechanisms and improving the stability of the mPendle peg. These changes are necessary to:
- Avoid unnecessary impermanent loss caused by the CAKE LP establishment.
- Stabilize the mPendle peg by reducing its market circulation.
- Ensure sufficient reserves for PNP bribes and operational needs.
- Enhance Penpie’s liquidity pools to attract more partner protocols and increase ecosystem participation.
Penpie’s revenue mechanisms require adjustments to address inefficiencies and adapt to the protocol’s evolving operational and ecosystem needs. While PIP #15 designated 20% of vePendle revenue for the recovery mechanism outlined in the Recovery Plan, the remaining revenue will be addressed through the strategies outlined in this proposal
- VOTER Revenue Adjustment
- Previous Version:
Revenue was used to establish the mPendle/Pendle Liquidity Pool (CAKE LP), as proposed in PIP #12. This approach aimed to stabilize mPendle’s peg but has resulted in a high surplus with low utilization and the risk of impermanent loss. - Proposed Change:
Suspend the establishment of the CAKE LP to avoid further impermanent loss and over-pegging of mPendle. Instead, mPendle tokens from buybacks will be temporarily stored in the treasury wallet until a new proposal determines their optimal use.
- BASE Revenue Utilization
- Previous Version:
All BASE revenue was allocated for PNP buybacks, with excess PNP stored in the treasury wallet. This mechanism ensured bribe incentives for protocols but resulted in underutilized assets. - Proposed Change:
Allow the team to use BASE revenue more flexibly to incentivize Penpie’s liquidity pools, fostering partnerships and increasing protocol cooperation. After meeting PNP monthly expenditure needs (e.g., bribe incentives for Cakepie, Penpie, and future SubDAOs), the remaining BASE revenue will be allocated as follows:- 30%-70% for mPendle buybacks (percentage determined by market conditions).
- Remaining funds for PNP buybacks. All assets will be stored in the treasury wallet for potential future use or proposals.
- OTC Purchases of mPendle Below Market Price
- Authorize the team to purchase mPendle via OTC at below market price, providing cost-effective accumulation and reducing the potential market impact of large buy orders.
- If the price exceeds market value, DAO approval will be required.
- Ensure transparency by announcing purchase quantities and amounts on official channels after OTC transactions are completed.
## Specification
This proposal requires voters to decide on the following adjustments to Penpie’s revenue mechanisms:
- Suspend CAKE LP Creation: Halt the use of VOTER revenue for establishing the mPendle/Pendle Liquidity Pool. Store mPendle buybacks in the treasury until a future proposal.
- Reallocate BASE Revenue:
- Use BASE revenue for PNP bribe incentives and operational needs.
- Allocate 30%-70% of remaining funds for mPendle buybacks, with the rest for PNP buybacks.
- Authorize OTC Purchases of mPendle: Permit OTC acquisitions below market price. Require DAO approval for purchases above market value.