PTIP-56
Simple Summary
Optimize parameters on the V3 pools for the transition to V4.
Motivation
PoolTogether V4 offers depositors a radically improved experience over the V3 protocol. As of now, there are no new deposits into PoolTogether V3 contracts.
However, the PoolTogether protocol is non-custodial which means the deposits in V3 can not be moved by the protocol, POOL holders, or anyone else. Additionally, it means the pools cannot be shut down. They will run forever.
Although the deposits can not be moved and the pools will run forever, there are certain parameters that governance can control. These parameters can be optimized for 1) the smoothest and best experience for the remaining V3 depositors and 2) minimization of costs to the protocol for operations.
Specification
This PTIP proposes a two phase approach, phase one stops new deposits and minimizes operations. Phase two leaves continued pool operations up to the community.
For phase one, the following parameter adjustments are proposed for the USDC, Dai, COMP, GUSD, and UNI pools on Ethereum.
- Set liquidity cap to $0 (this will prevent future deposits)
This one is pretty self-explanatory, setting the liquidity cap to $0 means any newly attempted deposits will fail. This will prevent new deposits so people can deposit into V4.
- Set reserve rates to 0%
The purpose of the reserves is fueling the “perpetual growth” machine of the protocol. The reserves were turned on for this specific purpose. PTIP-54 moved the v3 reserves to V4. Because all growth and reserves are now in V4 it makes sense and is most fair to depositors to correspondingly turn off the reserves on V3.
- Set RNG to blockhash
The prizes are so low that the Chainlink VRF is no longer needed. Setting the RNG to the future blockhash will be sufficient, and will save us time and remove the need to stock the strategies with LINK.
- Reduce number of winners to 1
This will radically lower the cost of awarding the pools.
Rationale
In combination, these settings will
- Ensure no new deposits can be made
- Ensure legacy depositors are treated in the most fair way possible
- Greatly reduce the transaction fees needed to award the pools
- Set the stage for the protocol to turn awarding over to the community
Status
- Support
- Oppose
0 voters
UPDATE:
Based on feedback below and technical considerations for the proposal (the maximum number of transactions per proposal). This proposal will initially move forward with solely 1) liquidity cap and 2) RNG to blockchash. That will then set the stage to implement the other elements of this proposal when the awarding is stopped and therefore the reserves will not need to cover it.