[GIP-105] DAI/USDT/GHO Pool additional configuration

Note: this is an optimistic proposal that applies to transactions from GIP-103. This means that transactions from GIP-103 with changes listed in GIP-105 will be queued before GIP-105 finishes voting. If GIP-105 is rejected, then the entire batch of transactions will be cancelled by the veto multisig.

Overview

This proposal aims to correct some deployment parameters for USDT, DAI and GHO pools that were overlooked in the initial GIP-103 proposal:

1. sUSDe quota limits for new pools will be set to 0, as Ethena expressed that at the moment they do not want the total size of sUSDe positions on Gearbox to go beyond 10M (which is already filled by USDC). This can be raised in the future to 3M for each pool without additional voting by the main multisig or through ControllerTimelockV3;
2. The quota limits for USDe in DAI and USDT pools are increased to 5M. The limit for the GHO pool will remain at 3M, as in the original proposal. All USDe limits in these pools can be raised to 10M without additional voting by the main multisig or through ControllerTimelockV3;
3. Max quota rate for USDe and sUSDe in the new pools will be set to 50%, to bring it in line with the updated rates from GIP-102;

Configurations files

DAI Pool: https://github.com/Gearbox-protocol/sdk-gov/blob/bd6728bf667ca451b92550b2cb497cb0a8027c20/src/config/configs/daiConfigMainnet.ts

USDT Pool: https://github.com/Gearbox-protocol/sdk-gov/blob/bd6728bf667ca451b92550b2cb497cb0a8027c20/src/config/configs/usdtConfigMainnet.ts

GHO Pool: https://github.com/Gearbox-protocol/sdk-gov/blob/bd6728bf667ca451b92550b2cb497cb0a8027c20/src/config/configs/ghoConfigMainnet.ts

Voting

Simple approve/reject.