KIR-1.1┃Choose AICK Deployment Chains

Integration Request (KIR)
1

Summary:

This proposal aims to choose the AICK deployment chains, a KUMA Interest-bearing token backed by KUMA NFT, themselves backed by AI Compute Equipment owned by Kaneda.

Rationale:

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

We propose to initially deploy the AICK on Plume Testnet.

Deploying the AICK 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:

  1. Smart contracts:

    • KUMASwap : Deployment for AICK
    • KIBToken : Deployment for AICK
    • KUMAFeeCollector : Deployment for AICK

  2. Setters on the KUMAAddressProvider smart contract:

    • setKIBTToken : Setter for AICK
    • setKUMASwap : Setter for AICK
    • setKUMAFeeCollector : Setter for AICK

  3. Setters sur le MCAGRateFeed :

    • setOracle : Setter for AICK

  4. Roles attributions :

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

Voting options:

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

Authors: Jean Brasse from Mimo Labs

Community poll:

  • Accept the deployment of AICK
  • Against the deployment of AICK / Rework the proposal
  • Abstain
0 voters