KIR-1 l Introducing AICK, backed by ‘Kaneda’ AI Compute Bonds


This proposal is introducing AICK, a KUMA Interest-bearing token backed by KUMA NFT, themselves backed by AI Compute Equipment owned by Kaneda.


Mimo Capital AG is currently working to tokenize Kaneda AI Compute corporate bonds in the form of KUMA NFTs. Mimo Labs proposes to accept this USD denominated NFT through the creation of the AICK by the Protocol.


Kaneda is a company which owns and leases GPU computing power (A100, H100, RTX 4090) specialized in training artificial intelligence models as well as Bitcoin ASIC. To boost growth, the company issued bonds, collateralized by these GPUs. The yield of the bonds comes from the yield generated by leasing the computing power of these GPUs. As the rental price is variable, the bond yield is also variable.

Note: The structure of these bonds is not yet definitive, and some parameters are still under discussion. This means that some information is missing, and will be made public at a later date. The proposal has been posted on the forum before the finalization of the structuration of the bonds in order to be able to reach the market as soon as the bonds are emitted and tokenized.

The AICK would be backed by Kaneda Corporate Bonds, tokenized on-chain as NFTs by Mimo Capital AG. Below are the informations of the KUMA NFT(s):

  • currency: USD
  • issuer: Kaneda
  • term: TBD

The expected yield of the bonds would range from 10% to 40% per year, depending on the yield of the underlying GPUs.

For a given riskCategory, there can be multiple individual bonds. For example the US treasury issues 1y government bonds every month, with the same inherent risk. We propose to accept the Kaneda riskCategory and its subsequent underlying to ease the integration of new bonds into Kuma Protocol for the AICK.

We propose to set up the SellBond Fee (via the ‘sellBond’ fees function) to 0.01%. This means that a fee of 0.01% is taken on each KIBT minted.

Since the yield of underlying bonds backing the AICK tokens will be floating, the AICK would be a non-rebase tokens, mainly due to technical limitations. It means that the quantity of tokens in the user wallet do not increase while the price of the asset is increasing over time.

Once the vote is accepted on Snapshot, the DAO will determine the chain(s) where the token would be deployed on a second KIR discussion.


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

Technical implementation:

  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 creation of AICK
  • Against the creation of AICK / Rework the proposal
  • Abstain

Authors: Jean Brasse from Mimo Labs

Community poll:

  • Accept the creation of AICK
  • Against the creation of AICK / Rework the proposal
  • Abstain
0 voters
1 Like