KIP-12┃Deploy the KUMA Protocol on Plume Testnet

Summary: Plume Network, in collaboration with Mimo Labs, proposes to deploy the KUMA Protocol on Plume Testnet.

Context Plume Network has spent these last few weeks working in collaboration with Mimo Labs, the company building the Plume chain, an Ethereum L2 focused on RWA, to propose the KUMA DAO to deploy the KUMA Protocol on Plume Testnet.

The proposal presents an overview of the KUMA smart contracts (the “KUMA Protocol”) with the main features as well as proposed KIBT(s) (already approved by the DAO) to be deployed. The proposal requests a vote from vMIMO holders regarding a potential deployment on Plume Testnet.

Rationale: Plume Network is a modular RWA L2 built to bring any real-world asset on-chain. In the context of real-world asset tokenization, here are the key points for deploying the Kuma Protocol on Plume Testnet:

• Regulatory Compliance: Plume Network integrates compliance and regulatory features directly into its Layer 2 solution, including KYC/KYB, AML/OFAC checks, and on-chain arbitration.
• Architecture: Plume's architecture includes custodians, account abstraction, and transfer agents, making it a secure and trustworthy platform for managing tokenized assets.
• Specialization: By deploying on Plume Testnet, Kuma Protocol can leverage Plume’s blockchain solutions focused on asset tokenization.
• Strategic Positioning: Plume’s Layer 2 solution positions Kuma Protocol as one of the go-to platforms for the growing demand for blockchain-based, compliant asset management solutions, potentially expanding its user base.

You can learn more about Plume Network here: https://plume.gitbook.io/plume

We propose to deploy only the USK on Plume Testnet: USK: The KIBT would be backed by 12 months US T-Bills, tokenized on-chain as NFTs by Mimo Capital AG. Below are the informations of the KUMA NFT:

• currency: USD
• issuer: US
• term: 12 (months)

Deploying the KUMA Protocol on Plume Testnet would open up new markets, both in terms of users, growth, and integrations; as well as taking the pulse of Plume's traction for a potential future deployment on Plume Mainnet.

Means:

• Human Resources: Multisig signers will need to sign transactions to execute the proposal
• Treasury Resources: There is no cost for the treasury to deploy the protocol on Plume Testnet. (as it is a testnet)

Technical implementation: If the proposal is approved, a second proposal will be posted detailing the protocol deployment plan.

Voting Options:

• Accept to deploy the protocol on Plume Testnet
• Against/Rework the proposal
• Abstain

Authors: Ivy Kang from Plume