This document will cover what’s needed to make the integration of Kima and your dApp a success. We’ll cover capabilities, expectations, and technology.

What is Kima?

Kima is a decentralized protocol, designed to bridge value between blockchains. Its target audience is dApp developers who’d like to enable participation of users from chains other than the one the dApp is deployed to.

Kima's components

  1. 1.
    Blockchain - the Kima blockchain is a decentralized application, built on top of Cosmos SDK. It utilizes several technologies to securely observe and enact foreign blockchain transactions. The Kima blockchain is based on Proof-of-Stake consensus.
  2. 2.
    KIMA token - the native utility token of the Kima blockchain. It’s used to pay for transactions on the chain, provide means for staking and delegation, and enable sharing revenues with stakeholders.
  3. 3.
    Pools - EOA accounts under the control of Kima blockchain. Each pool can have a balance of several tokens that can be bridged to other blockchains.
  4. 4.
    SDK - the set of tools allowing developers to integrate with Kima. They include a front end set of widgets, as well as wrapper around the Kima API.
  5. 5.
    Kima API - provided by Kima sentry nodes, this is an RPC interface allowing submitting transactions to Kima blockchain, as well as querying data and status.

Kima's use cases

Currently we identify 2 main use cases (many more to come):
  1. 1.
    Payment - a user on chain X wants to acquire a service/product from a dApp deployed to chain Y. In this use case the dApp developer controls the destination address.
  2. 2.
    Bridge - a dApp developer wants to enable his users to move liquidity between 2 chains - regardless of where the dApp is deployed. In this use case the controls both origin and destination addresses, and the dApp simply acts as an intermediary.
Last modified 9mo ago