KIR-2.1┃Choose BTCMK Deployment Chains

Summary: This proposal aims to choose the BTCMK deployment chains, a KUMA Interest-bearing token backed by KUMA NFT, themselves backed by Bitcoin ASIC Equipment owned by Kaneda.

Rationale: With the recent vote in favor of the launch of BTCMK, a KUMA Interest-bearing token backed by KUMA NFT, themselves backed by Bitcoin ASIC Equipment owned by Kaneda; the DAO needs to determine the chain(s) where the KIBT would be deployed.

We propose to initially deploy the BTCMK on Plume Testnet.

Deploying the BTCMK on Plume Testnet will make it possible to test the new model of non-rebasing KIBT while participating in the Plume Testnet campaign. This to increase traction and brand in the Plume Ecosystem.

Means:

• Human resources: If the proposal is approved, the KUMA Multisig signers will have to execute the proposal following the voted technical implementation and deploy the protocol on Plume Testnet.
• Treasury resources: There is no treasury cost.

Technical implementation: On Plume Testnet:

• Smart contracts:

  • KUMASwap : Deployment for BTCMK
  • KIBToken : Deployment for BTCMK
  • KUMAFeeCollector : Deployment for BTCMK

• Setters on the KUMAAddressProvider smart contract:

  • setKIBTToken : Setter for BTCMK
  • setKUMASwap : Setter for BTCMK
  • setKUMAFeeCollector : Setter for BTCMK

• Setters sur le MCAGRateFeed :

  • setOracle : Setter for BTCMK

• Roles attributions :

  • Attribution of KUMA_MIN_ROLE to each KUMASwap contract : Attribution for BTCMK
  • Attribution of KUMA_BURN_ROLE to each KUMASwap contract : Attribution for BTCMK

Voting options:

• Accept the deployment of BTCMK
• Against the deployment of BTCMK / Rework the proposal
• Abstain

Authors: Jean Brasse from Mimo Labs