MIP-14.2 | paUSD launch, Ethereum deployment plan

Improvement Protocol (PIP) Approved PIPs
1

Summary:
This proposal aims to determine the deployment plan for paUSD on Ethereum.

Context
Few weeks ago, MIP-14 & MIP-14.1, which are introducing the paUSD and their first tokens as collateral, was approved by the DAO. Following this, and in view of the imminent launch of the paUSD on Ethereum, the DAO must determine the deployment plan of the protocol on Ethereum.

Rationale:
The deployment of smart contracts cannot be performed via the Parallel Protocol multisig. A wallet created especially for the occasion will be used to deploy the smart contracts, the ownership of these smart contracts will then be transferred to the Parallel Protocol multisig.

Below is the proposed detailed plan for the deployment of paUSD smart contracts:

Core :

  • AccessController : single deployment
  • AddressProvider : single deployment
  • ConfigProvider : single deployment
  • paUSD : single deployment
  • PriceFeed : single deployment
  • RatesManager : single deployment
  • LiquidationManager : single deployment
  • FeeDistributor : single deployment
  • VaultsDataProvider : single deployment
  • VaultsCore : single deployment
  • DebtNotifier : single deployment

Governance :

  • GovernanceAddressProvider : single deployment
  • DebtNotifier : single deployment

Liquidity Mining :

  • SupplyMiner : one deployment for each collateral

Setters on AddressProvider :

  • setAccessController : single setter
  • setConfigProvider : single setter
  • setVaultsCore : single setter
  • setStableX : single setter
  • setRatesManager : single setter
  • setPriceFeed : single setter
  • setLiquidationManager : single setter
  • setFeeDistributor : single setter
  • setVaultsDataProvider : single setter

Setters on GovernanceAddressProvider :

  • setParallelAddressProvider : single setter
  • setMIMO : single setter
  • setDebtNotifier : single setter

Setters on ConfigProvider :

  • setCollateralConfig : one setter per collateral

Setters on VaultsCore contract :

  • setDebtNotifier : single setter

Setters on PriceFeed contract :

  • setAssetOracle : one setter per collateral

Setters on FeeDistributor contract :

  • changePayees : single setters with VaultsCore getting 100% of the shares as initial setting

Setters on DebtNotifier contract :

  • setCollateralSupplyMiner : one setter per SupplyMiner

Role granting on AccessController contract :

  • MINTER_ROLE to VaultsCore contract
  • MINTER_ROLE to FeeDistributor contract
  • MANAGER_ROLE to DAO multisig

Transfer of roles to the DAO multisig :

  • DEFAULT_ADMIN_ROLE
  • MANAGER_ROLE

Revoke deployer key roles :

  • DEFAULT_ADMIN_ROLE
  • MANAGER_ROLE

Means:

  • Human resources: If the proposal is accepted, the Parallel Multisig signers will have to execute the proposal following the technical voted implementation.
  • Treasury resources: There is no treasury cost.

Technical implementation:

Described in the proposal.

Voting options:

  • Accept the deployment plan
  • Against the deployment plan / Rework the proposal
  • Abstain

Authors: @JeanBrasse from Mimo Labs

Community poll:

  • Accept the deployment plan
  • Against the deployment plan / Rework the proposal
  • Abstain

0 voters

4 Likes
2

Yessss, let‘s go ser :saluting_face:

3 Likes
3

With more than 5,5vMIMO, the MIR-14.2 has been approved

Result: Snapshot