After the transaction is written to the Kima appchain, Kima’s liquidity managment engine, LiMa, kicks into gear. this allows Kima to balance out the pools, providing the end-user with liquidity in their target chain.

since the pools only contain native assets, LiMa is there to make sure that there’s always enough liquidity to settle pending transactions. This is very useful for liquidity providers, as LiMa offers liquidity bounties for pools that need replenishing.

Liquidity arrives

at target chain

The last step is where Kima debits the source chain and credits the target chain. This means that funds are never taken out before being sufficiently validated in Kima’s pools, providing high capital security, efficiency and near-constant reversibility. Until this step, the end-user is aware of every step and can revert the transaction.

After this step, Kima sends the funds from the target chain’s pool to wherever they need to go: Either the end-user’s target wallet or to the host dApp directly, depending on the specific use case Kima was implemented for.

$KIMA #Kimanetwork