KIP-2.2┃KUMA Protocol on Ethereum, Deployment Plan

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

Context: Last week, KIP-2, which is introducing the KUMA Protocol, was approved by the DAO. Following this, and in view of the imminent launch of the KUMA Protocol, the DAO must determine the deployment plan of the protocol on Ethereum.

Rationale: The deployment of smart contracts cannot be performed via the KUMA Protocol multisig 1. 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 KUMA Protocol multisig 1.

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

1. Smart contracts:

• KUMAAccessController : single deployment
• KBCToken : single deployment
• KUMAAddressProvider : single deployment
• MCAGRateFeed : single deployment
• KUMASwap : Deployment for USK (1 deployment per risk category)
• KIBToken : Deployment for USK (1 deployment per risk category)
• KUMAFeeCollector : Deployment for USK (1 deployment per risk category)

2. Transfer of roles to the KUMA Protocol multisig: -DEFAULT_ADMIN_ROLE

• KUMA_MANAGER_ROLE
• KUMA_SET_EPOCH_LENGTH_ROLE
• KUMA_SWAP_PAUSE_ROLE
• KUMA_SWAP_UNPAUSE_ROLE
• KUMA_SET_URI_ROLE

3. Setters on the KUMAAddressProvider smart contract:

• setKBCToken : single setter
• setRateFeed : single setter
• setKUMABondToken : single setter
• setKIBTToken : Setter for USK (1 setter per risk category)
• setKUMASwap : Setter for USK (1 setter per risk category)
• setKUMAFeeCollector : Setter for USK (1 setter per risk category)

4. Setters sur le MCAGRateFeed :

• setOracle : Setter for USK (1 setter per risk category)

5. Roles attributions :

• Attribution of KUMA_MIN_ROLE to each KUMASwap contract : Attribution for USK (1 attribution per risk category)
• Attribution of KUMA_BURN_ROLE to each KUMASwap contract : Attribution for USK (1 attribution per risk category)

Means:

• Human resources: If the proposal is approved, the KUMA 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