Delegating your $KIMA tokens has multiple benefits. Most of these are related to enhancing network security, reducing operation complexity and increasing participation.

Enhanced Security

Delegation allows for a wider distribution of decision-making power and staking responsibilities, thus reducing centralization.

Reduced operation complexity

A delegator who may not have the required technical expertise or resources to run a validator node can still participate in staking. Additionally, the amount required to run a validator often exceeds the funds a typical user might hold.

Delegation also allows delegators to diversify their portfolios by designating some tokens for delegation while keeping others for active trading or investment.

Increased participation

Delegators can participate in network decisions without having to manage the technical aspects of voting or governance. They can rely on validators to handle these aspects while still staking their tokens to influence network decisions.

Welcome to the Delegation documentation section. This guide covers everything you need to know about delegating to a validator, including the benefits, technical workings, and step-by-step instructions.

If you want to dive deeper, you can find more technical detail in the two papers that are linked below.

White Paper

Tech Paper

This section describes how to upgrade the SDK to the latest version. There are 2 components to upgrade:

1. The frontend React Component: The Widget

2. The backend API: The Transaction Backend

Generally speaking, the Widget and Backend should have the same major and minor versions- i.e. 1.4.x and 1.4.x. See the specific instructions for the version you are upgrading to. If you are upgrading more than one minor version at a time, see the instructions for each minor version for the extra steps.

Delegation is a process that facilitates efficient governance, consensus and operational management in a blockchain.

A participant in the network - a delegator - assigns their voting rights, governance power, and/or staking responsibilities to another participant, referred to as the delegate. This is often a validator of the network.

Why choose to delegate?

This process allows every token holder to participate in the staking process without running their own validator. The validator receives yields from the staking process for validating transactions directly. Then the validator shares a portion of the corresponding rewards with each delegator while taking a percentage of the rewards for being the delegate. Each validator can adjust the commission percentage to incentivize more participants to become delegators.

In Kima, delegation locks the tokens for a period of time. This prevents misuse of the delegation and instant withdrawals after receiving rewards or participating in network decisions.

Please read the terms and conditions, privacy policy and disclaimer.

Transparency is one of the key features of public blockchain technology, and block explorers such as Etherscan provide users with an assurance that their transactions are being processed in a timely manner, as well as providing various other insights.

Kima's block explorer for Sardis Testnet is an essential dashboard showing key facts about the state of the network, including transaction history.

If you are developing on Sardis Testnet, this is where you will be able to monitor your transactions:

https://explorer.sardis.kima.network/

The Kima demo app serves two purposes:

• to showcase payments and bridging using Kima

• to illustrate the look and feel of the Kima front-end widget

The Kima Demo supports the following testnets:

• Ethereum Sepolia (*)

• Polygon Amoy (*)

• Avalanche Fuji

• Tron Nile Testnet

• Optimism (Sepolia)

• Arbitrum (Sepolia)

• Binance Smart Chain Testnet (aka BNB Testnet)

• Base Sepolia

• Berachain Bepolia

• Solana Devnet

(*) Not available in light mode

To enable a smooth experience and a 360-degree overview of what is happening, we also provide a and a .

The Kima Network has an on-chain governance mechanism for signaling (text proposals), changing parameters and allocating funds from the community pool.

Community​

Kima governance is driven by the Kima community. Proposals can be followed here.

Because the Kima blockchain is a public network, you can interact with it however you see fit. You can choose to become a validator, if you want - see Becoming a Validator for more details - or you can build a variety of applications on top of it.

To make developing on top of Kima simpler, we have created a toolkit - the Kima Software Development Kit (SDK).

We provide:

• a standalone server that you can run locally and use as middleware that sits between the front end of your dApp and the Kima blockchain, submitting requests and returning the response to the front end

• a front-end widget with different configuration options that you can easily integrate into your dApp

Of course, the open ethos of Web3 means that you can develop your own solutions from scratch, but we strongly recommend building with both front end and back end components of our SDK so you can leverage the efforts our development team have made on your behalf.

There is an extra step that may be required in some test environments if you are using Kima's tools to transfer to or from Solana wallets. In those environments, the recipient wallet may need to be "primed" by receiving a small amount of USDK before transfers or payments via Kima can take place.

The Kima Transaction Widget is a ready made React component that allows users to transfer like assets between chains using the Kima protocol. Combined with the Kima Transaction Backend, it is the quickest way to integrate Kima into your dApp.

The Kima Transaction Widget supports 3 modes:

1. Payment

2. Bridge

3. Status

The Kima blockchain relies on a network of validator nodes for its security and consensus. KIMA tokens are distributed to validators as an incentive for their participation in the network.

You can read more about both Kima's incentive model and its innovative security architecture in the

Two areas of Kima's security architecture stand out:

• Threshold signature schemes (TSSs) allow a group of participants (“cosigners”) to securely generate and control the secret signing key for a digital signature scheme, such that a certain threshold (e.g. 2-out-of-3 or 7-out-of-10) cosigners must participate in, and agree upon, the signing protocol in order to generate a signature.

• To further complement security, Kima wardens run the threshold signature scheme inside an SGX enclave, thus the TSS key-shares are not directly accessible to the wardens or their system administrators.

The Kima Demo is a reference implementation to help people understand how Kima works.

You will need to have a wallet installed and to have some USDK (Kima's US dollar stablecoin) in your wallet on the testnet you want to use. This page explains how to do this. Remember that you will also need a small amount of the native token for the testnet you are sending funds from so you can pay for gas (for example, you will need Sepolia ETH if you want to send from Etherum's Sepolia testnet).

The demo showcases the following scenario:

• bridge between different chains (transfer to the same or a different address on different chains). Example: a user has funds on Avalanche but wants to add liquidity to a liquidity pool on Ethereum.

This demo allows us to send funds to our own or a different wallet address on a network of our choice. Here we are sending USDK from Arbitrum's Sepolia testnet to Avalanche's Fuji testnet.

The following are parameters that are currently present in the governance process:

• Minimum deposit: 10,000 KIMA

• Maximum deposit period: 14 days

• Voting period: 7 days

mode = ModeOptions.bridge

Bridge mode allows your users to transfer similar assets between any chain supported by Kima. I.e. USDC on Arbitrum to USDT on Avalanche.

On testnet it should look something like this. The test tokens are called USDK and can be obtained from the .

The transfer details will show on the next step, along with the fee options available. The confirmation step will also request user approval on the final transfer amount.

The transaction status will be displayed on the next step when the user approves the transfer amount and submits the transaction.

For more details on how to get transaction status of a previous transaction, check the .

The Kima Light Demo is a reference implementation to help people understand how Kima works.

You can experience Kima's functionality directly in your browser, without needing to install or connect a wallet because the Light Demo App has been pre-configured to send funds between two accounts under the control of the Kima team.

The demo showcases bridging between different chains (transfer to the same address on different chains). Example: a user has funds on Arbitrum but wants to add liquidity to a liquidity pool on Avalanche.

Use the dropdown to choose the network from which you want to send funds. A demo wallet address will be automatically assigned for that network.

Use the second dropdown to choose the destination network. Another demo wallet will be auto-selected to receive the funds.

Type the amount of USDK you want to transfer.

Add the widget to your React project using npm or your favorite JavaScript package manager.

You'll need to add the following:

• The <KimaProvider> component in App.tsx

• The <KimaTransactionWidget>

To quickly connect to the Kima testnet, you can use managed services like Infura, Alchemy, QuickNode, or Ankr. These services simplify blockchain infrastructure by providing RPC endpoints you can access with API keys.

Here’s how to create API keys for each service:

When selecting networks ensure you select the Kima-supported networks (see the ).

Infura

Visit the and create an account. Follow the prompts to create an API key.

Alchemy

Sign up at Alchemy's website. Navigate to the dashboard and select Apps in the left-hand menu. Create a new App, selecting the network(s) you need. Once saved, your API key will be displayed at the top right of the page.

QuickNode

Sign up at

Kima offers significant incentives for liquidity providers, whether they participate passively or actively. By joining our liquidity pool system, providers can maximize their returns and help secure cross chain liquidity, benefiting from Kima’s efficient and secure network.

Liquidity providers earn a portion of the network transaction fees. For every transaction processed through the liquidity pool, a small fee (0.05% of the transaction amount) is distributed to liquidity providers. Example: For every $1 million in daily transaction volume, liquidity providers earn $500 in network fees per day, or $182,500 annually. Passive liquidity providers, in this case, would receive half of that amount ($91,250/year).

Kima is designed to achieve high capital efficiency, meaning liquidity providers can earn more returns with less liquidity.

Kima’s liquidity pools span multiple blockchain networks, offering liquidity providers access to a broad range of opportunities. By providing liquidity across Ethereum, Polygon, Optimism, and other networks, providers can participate in various ecosystems while enjoying the benefits of Kima’s seamless cross-chain infrastructure.

Kima Finance leverages Trusted Execution Environments (TEEs) and a Threshold Signature Scheme (TSS) to ensure that all liquidity provider operations are secure and private. These advanced security mechanisms protect liquidity providers' assets while enabling the system to function at optimal performance.

Kima is the world’s first infrastructure-agnostic money transfer protocol. The Kima platform is comprised of a blockchain and a toolkit that allows the seamless transfer of assets between different protocols and platforms.

Blockchains are siloed. Web3 apps built within those ecosystems are constrained by their on-chain liquidity. Many solutions developed for these challenges, known as bridges, suffer from flaws and vulnerabilities: security, user experience, complexity, and poor capital efficiency.

Kima addresses these challenges in a unique way, by creating a Web3 settlement layer which enables interchain transactions. This approach allows liquidity to be transferred between chains in a safe, secure, and cost-effective manner, enabling a reliable omnichain solution.

Security: Kima achieves unique security by eliminating all known attack vectors (no smart contracts, no oracles, no external relayers) and adding multiple layers of security (e.g., using a Trusted Execution Environment with Intel SGX and decoupled validation). The protocol uses game theory and financial incentives to maintain liquidity equilibrium and maximize capital efficiency.

Infrastructure: Kima simplifies and accelerates the creation of secure Omnichain applications, tackling interoperability problems without causing additional liquidity fragmentation. It provides a mechanism for users to perform cross-chain atomic swaps without token-wrapping.

The Kima blockchain, built using the Cosmos SDK, employs a committee-based consensus. "Wardens" in a rotating committee ensure asset pool synchronization and authorize withdrawals based on corresponding deposits. This structure uses Threshold Signature Schemes (TSS) and operates within a Trusted Execution Environment for enhanced security.

1. If you haven't already,

2. Open Keplr, click the hamburger menu, and select "Add more chains" at the bottom (alternatively, you can browse to )

3. Connect your Keplr wallet

During the initial release period of Kima, the only supported assets will be USDC and USDT on EVM, Tron and Solana. More assets and blockchains will be added in later releases. Assets marked “optional” will be added on demand.

This guide will help you learn how to provide liquidity for the Kima protocol.

• Understand the Benefits: Start by reviewing the section to learn about the incentives, rewards, and advantages of providing liquidity for Kima.

• Review Supported Assets and Networks: Before proceeding, familiarize yourself with the section to understand which assets and networks are currently supported by Kima.

To withdraw an asset on any blockchain in the Kima Finance protocol,follow these steps:

Step 0: Ensure Liquidity Balance

Before withdrawing liquidity, make sure:

• You have assets available for withdrawal.

• You have at least 0.2 Kima tokens in your Keplr wallet.

Step 1: Select the amount and network

Choose the amount you would like to withdraw.

Select the network from which you want to withdraw.

Once you have set the amount and network, click Withdraw to remove liquidity from the chosen pool.

Upon clicking Withdraw, a New Transfer window will appear. In this window:

Connect your wallet if it is not already connected.

Review the transaction details, including the source network, wallet address, and withdrawal amount.

After reviewing the transaction details, click Next to move to the confirmation step.

In this step, you'll need to approve the transaction, which allows the transfer of the liquidity from the pool you selected to your wallet.

Click Approve to proceed with the transaction.

For all transactions on the Kima Finance network, you will be asked to make two approvals through your Keplr wallet.

Important: You may have to wait a few seconds for the second approval request to appear. If the Keplr wallet does not automatically launch, open it manually to see the pending approval requests.

Once you’ve signed and approved both requests, the transaction process will begin.

Once the transaction reaches 100% completion, your asset’s liquidity will be withdrawn from the pool to your wallet.

You can verify your current liquidity assets still deposited with Kima.

Kima supports a variety of EVM-compatible Layer 1 and Layer 2 chains, as well as Solana, and will ultimately allow the swift and secure transfer of value between the following blockchains:

The short names are used in various API queries. Most are shared across mainnet and testnet, while some can be environment-specific. For a full environment-wide chain inventory, use get_chains. For route-specific destinations from a given origin chain, use get_available_chains/{originChain}. Click on the chain ID link to visit Chainlist.org and add the chain to your wallet.

ℹ️ Credit Cards and Bank Accounts are currently supported as the origin network- off ramping to come in a future release. ℹ️ In backend request payloads, FIAT rails may be represented as CC and BANK, then normalized to FIAT before submission. ℹ️ Documentation uses Berachain and Berachain Bepolia as display names. API responses may use Bera or Berachain, while the stable short name remains BERA.

Kima is currently available on the following testnets, which can be used for development and/or testing in the Kima Demo App:

Use get_chains if you want the full list of chains available in a given environment:

• Mainnet: https://api.kima.network/kima-finance/kima-blockchain/chains/get_chains

• Testnet: https://api.sardis.kima.network/kima-finance/kima-blockchain/chains/get_chains

Response:

• Chains: string[]: the list of supported chain short names for that environment

Use get_available_chains/{originChain} if you want the set of destination chains available from a specific origin chain:

• Mainnet: https://api.kima.network/kima-finance/kima-blockchain/chains/get_available_chains/{originChain}

• Testnet: https://api.sardis.kima.network/kima-finance/kima-blockchain/chains/get_available_chains/{originChain}

Params

• originChain (string): the starting chain short name (see above)

Response

• Chains: string[]: the list of chain short names which can be bridged to from the origin chain

The example above reflects a mainnet query using originChain=ETH on March 10, 2026.

Kima Faucets

Kima has two testnet faucets: one for the native KIMA token and one for the Kima stablecoin, USDK. You will need KIMA tokens for development purposes. You will need testnet USDK to interact with the Kima platform on whatever testnets you are developing on, and also if you would like to use the Kima Advanced Demo App. The faucet will give out 100 USDK daily per wallet address. Note that these are testnet tokens only and have no financial value or benefit

Instructions for USDK faucet - EVM chains

1. You will first need to have an EVM-compatible wallet installed in your browser, such as MetaMask or Rainbow, if you do not already have one installed. Note that Kima does not endorse, recommend or guarantee any specific wallet. Follow the installation instructions and ensure that you keep your seed phrase safe.

2. Visit the faucet site.

3. Select the network you want to send funds from, whether this is for payment or bridging.

1. Connect your wallet by clicking the Connect button.

2. Your screen should now look like the screenshot below. Go ahead and click the Get Free 100 USDK button.

Note that in order to send funds from a particular network, you will also need a small amount of that network's native token in order to pay for gas costs.

So, for example, to bridge or pay from Ethereum's Sepolia network, you will need a small amount of Sepolia ETH, which can be acquired from any Sepolia faucet.

To acquire testnet USDK on Solana or Tron, the process is broadly the same but you will need to use a wallet that is compatible with these chains.

While we at Kima do not endorse or guarantee any particular wallet, we note that Phantom is a popular choice for interacting with Solana and TronLink is a popular choice for Tron, so we will demo the use of these two wallets in obtaining testnet USDK.

You will need to manually switch your wallet to use Solana's Devnet. Solana faucet

From here, you can connect your wallet and request tokens as described in steps 4 to 6 above.

Again, you will need to manually switch your network in your TronLink wallet to use the Nile testnet. You can do this by clicking on the down arrow in the middle of the top navigation bar where the current network is displayed, as shown in the image below. Tron faucet

From here, you can connect your wallet and request tokens as described in steps 4 to 6 above.

1. You will first need to have a wallet installed that is designed to interact with the Cosmos ecosystem, such as Keplr.

2. Visit the .

3. Connect your wallet by clicking the Connect button.

1. Go ahead and click the Get Free 10 KIMA button.

1. The request will be processed and your tokens will arrive once its the transaction succeeds. You can also check the transaction details in the explorer.

REMINDER: you can send tokens request only once per 24 hours.

ℹ️ Kima is constantly updating the available payment and settlement methods, currencies, and supported countries - stay tuned.

Fiat support

Kima manages several fiat pools as regulated bank accounts that can only be accessed following blockchain consensus, and TSS signature - just like the Kima crypto pools. This allows Kima to receive, and emit fiat payments.

Kima intends to offer the following settlement methods in the future:

• Pay-in/Fiat on-ramp - pay with fiat, receive crypto

• Pay-out/Fiat off-ramp - pay with crypto, receive fiat

• Exchange/Fiat FX - pay with one fiat currency, receive another

ℹ️ Currently, Kima supports Pay-in/on-ramp settlements.

ℹ️ Currently, Kima supports credit cards, and bank accounts in Europe using SEPA and SWIFT. Additional payment methods coming soon.

• US Dollar

• EURO

ℹ️ Other currencies coming soon.

Any credit card payment originating in the following countries will be blocked:

• Belarus

• Cuba

• Iran

• Myanmar

ℹ️ Support for U.S. and its territories coming soon.

The following credit cards are currently not accepted:

• American Express

ℹ️ Support for additional credit cards coming soon.

mode = ModeOptions.status

Status mode displays the progress of a transaction that has already been submitted to Kima. This is useful if the normal flow was interrupted and the status needs to be displayed again. Usually the transaction status view will display automatically after the user approves and submits the transaction.

⚠️ txId is the transaction id returned from /submit/transfer or /submit/swap - not the transaction hash. I.e 22843

const App = () => {
  return (
     <KimaProvider
      projectId='your-project-id'
      kimaBackendUrl="http://localhost:4000"
    >
      <KimaTransactionWidget
        theme={{ colorMode: ColorModeOptions.dark }}
        mode={ModeOptions.status}
        txId={22843}
      />
    </KimaProvider>
  );
};

You would see a page that looks like this:

If you want to allow users to get a previous transaction from the UI, you must not provide the txId prop to the KimaTransactionWidget component. This will display the transaction search form.

If the transaction id is valid, and the transaction is found, the corresponding progress of the transaction will be displayed.

Kima Use Cases for Developers

As a developer, what can you build with Kima? In order to onboard more users to Web3, we need to simplify the user experience, which means helping them avoid complicated procedures on bridging applications that may or may not be safe to use.

Integrating with Kima's SDK or front-end widget removes the need for your users to leave your dApp and enables them to effortlessly switch funds between networks with the click of a button.

You could think about using Kima for:

Decentralized Exchanges (DEX)

A quick glance at DeFi Llama shows that Ethereum's share of TVL is dropping as DEXs choose to deploy on different networks. Allowing users to bridge funds via a plugin on your own website provides them with a seamless user experience, whichever chain they want to use.

eCommerce and Gaming

In-game payments can slow down the user experience and add unwanted friction. If your users also have to bridge their funds between chains, this can introduce frustration and boredom that may lead to them abandoning your game completely. Kima's smooth, intuitive transactions will mean your users barely notice them.

Similarly, buyers on eCommerce sites are more likely to proceed through the sales funnel if their experience is not impeded by having to visit a separate bridging application.

NFT Marketplace

NFT collectors are no longer limited to one or two chains, and some of the coolest up-and-coming collections can be found on minority chains where fees are cheaper and transactions are faster. Make your marketplace effortlessly multi-chain by integrating Kima.

Wallet developers looking for an easy, intuitive way for their users to swap assets in-wallet need to look no further than Kima.

Essentially, as the number of networks within the thriving Web3 ecosystem expands, the need for sending value securely and quickly from one chain to another has become a pressing need.

If you are planning to undelegate for the purpose of switching validators, unstaking funds to use elsewhere, or just taking a break, follow the steps below. When you undelegate your tokens on the Kima network, they enter an Unbonding period of 21 days, which means they are locked until the period ends before being transferred back to your wallet. This ensures commitment to the KIMA network and prevent abuse and misuse of the delegation process.

This guide assumes you have previously delegated tokens on Kima.

Connect your wallet

Go to the KIMA explorer and click the Connect Keplr button.

Testnet explorer Mainnet explorer

Approve the prompts.

In the explorer, click the Overview tab in the left sidebar of the home screen.

Scroll down until you can see the Delegations section. There, you should be able to see a summary of your delegated stake among the available validators.

Look for the delegated stake that you plan to undelegate and click on the Undelegate button.

Enter the amount of $KIMA you want to undelegate and click on Submit.

You will be prompted to approve the transaction. To confirm, click on Approve.

In the Delegations section, you should see that you no longer have any delegated stake. Your undelegated tokens will be in the Unbonding period.

After this period, you will be able to view your tokens in your wallet.

In this guide, you will learn how to set up a wallet and add funds to it. This process can vary depending on whether you're using the mainnet or testnet. We'll cover the following scenarios:

• Setting up a wallet

• Using a faucet (testnet only)

Set up a wallet

Choose a wallet

Some wallet options are Keplr (recommended), Station and Leap.

Install the wallet

Then select your preferred browser/device. This guide shows the installation process using Google Chrome.

Add the wallet as a Chrome extension. To minimize risk, always verify that the team behind the extension corresponds with the Keplr app.

Click the Add to Chrome button and wait for the extension to open a new tab with the setup steps. Click the Create a new wallet button to begin the setup.

This will prompt you to choose a wallet creation method.

Read the security concerns about creating a new wallet using a recovery phrase carefully, and click 'I understood. Show my phrase.' Store that phrase in a secure place where only you can access it.

Now enter the words requested from your recovery phrase, add a name and a password to your wallet, then click Next.

Select the default networks and the setup will be completed.

Note that this step applies to the testnet only.

Kima has available faucets for both its native token ($KIMA) and the USDK stablecoin. To delegate on the testnet, you need to have $KIMA to execute the transaction and send the delegated amount.

For further reference, please visit the documentation.)

This guide uses the Next.js App Router pattern, which matches the maintained example in the widget repository. The widget must run on the client, so the widget component should be a client component and exported through dynamic(..., { ssr: false }).

To create a new app, you can run npx create-next-app@latest <your-app-name>. Then install the Kima Widget and its peer dependencies.

You'll need to add the following:

• A client-side widget component

In order to submit a transaction to the Kima blockchain, the user must sign a message containing the transaction details. This message is signed by the user's wallet and then included in data submitted to the Kima Transaction Backend submit endpoints (/submit/transfer or /submit/swap).

The Kima message is a string that is signed by the user's wallet. It contains the following information:

• Authorization amount: in whole tokens i.e. 10.23 not 10230000

mode = ModeOptions.payment

Payment mode allows your users to pay for a product or service using stablecoins from any chain supported by Kima.

• The payment details are passed into the Widget via the transactionOption prop (required)

• The user can choose to pay from any and supported by Kima. The funds will be transferred to the wallet and chain specified in the transactionOption

Welcome to Kima Foundation’s website (the “Site”). We are committed to protecting your privacy and ensuring that your personal data is handled in a safe and responsible manner. This Privacy Policy explains how we collect, use, disclose, and safeguard your personal data in compliance with Singapore’s Personal Data Protection Act 2012 (PDPA) and other applicable regulations.

This Privacy Policy applies to all personal data collected by Kima Foundation through the Site, including any other digital platforms, tools, or services operated by us. By using our Site, you agree to the collection, use, and disclosure of your personal data as described in this Privacy Policy.

We may collect personal data from you in the following ways:

• Directly from You: When you register, subscribe to our newsletter, participate in surveys, or contact us through our Site.

• Automatically: When you interact with our Site, we may collect data such as IP addresses, browser type, operating system, referring URLs, and usage patterns through cookies and other tracking technologies.

• Support for credit cards as an origin network (onramping)- off ramping to come in a future release

• Increased security by signing a message containing the transaction details

• More accurate fee estimation. This endpont also returns the amounts used for the allowance and submtting the transaction.

UPGRADING TO v1.4.x IS REQUIRED FOR ALL KIMA SDK USERS. These new features introduce breaking changes to how Kima tranasctions are submitted and processed. Once these features are live on mainnet, transactions sent using an older version of the SDK will be rejected by the chain.

Starting with version 1.5, Kima supports bank transfer transactions in the origin network (onramping)- off ramping to come in a future release. See for more information on how to upgrade your integration.

Bank transfer transactions require the use of the . This is a frontend React component which handles integration with Kima and 3rd party components which handle KYC and payment processing.

ℹ️ Check the list of

The following steps outline the process of using the widget to buy stablecoins like EURC using a bank account.

1. From the "Source Network" dropdown, select "Bank Transfer"

The Kima Widget serves as a reference implementation written in React. If your project uses another framework, or you want to make a custom component, it’s possible to interact with the Kima Transaction Backend directly. This page documents that backend-mediated integration path for crypto-origin and BTC-origin flows only. But:

🚨 FIAT TRANSACTIONS ARE ONLY SUPPORTED USING THE WIDGET 🚨

The frontend kima-transaction-widget is required for FIAT-origin flows such as credit-card and bank-transfer transactions because it handles KYC and interactions with 3rd party widgets.

1. User selects the origin and target chains and amount.

Prerequisites

Programs and applications

curl: Required for fetching external IPs and interacting with web services. Ensure it is installed and configured on your system. git: Needed for cloning repositories and managing code changes. Install it and ensure familiarity with basic commands. text editor: Use any editor (e.g., Vim, Nano) to update configuration files as needed

Currently, validators are selected manually and require access to private GitHub repositories. These repositories will be made open-source in the near future.

To gain access and prepare your environment, you must: 1. Set up an SSH key

• Generate an SSH key.

• Add the SSH key to your GitHub account. 2. Accept the repository invitation

• Once your SSH key is linked to your GitHub account, you will receive an invitation to access the necessary repositories. 3. Ensure required permissions and tools You will need sudo access on your machine to manage installations and configurations.

Ensure the git command is installed and configured, as it is required to clone the Kima repositories. Note: For assistance with setting up an SSH key or linking it to GitHub, refer to .

Proper SSH configuration and access permissions ensure secure and seamless repository access.

Public static IP

Open Ports:

• 22: SSH (Secure Shell) protocol

• 26656: Cosmos app CometBFT gossiping port for consensus

• 26657: Cosmos app CometBFT RPC port

• 9090: Cosmos app gRPC port

Download scripts from the Github repository to your server using any convenient method.

Make the files executable with:

Navigate to the validator directory:

Create an empty .env file:

Copy the template file to .env:

⚠️ Note: This will overwrite any existing .env file. Ensure you want to proceed.

In the same .env file, add the RPC and WSS endpoints for the blockchain networks you will connect to:

⚠️ Important: Use a high-performance RPC endpoint. Free or basic paid plans may not suffice. Replace <YOUR_INFURA_API_KEY> with your actual API key. Update the URLs and details for other networks as needed.

Suggestions for Testnet API Keys: Services like Alchemy, QuickNode, or Ankr support various chains, including Ethereum, Polygon, AVAX, BSC, and more. Refer to their documentation for API key acquisition and configuration.

📝 Tip: Check each blockchain's official documentation for the latest public testnet endpoints or additional API services.

Execute the following script to install necessary components and start the installation:

Upon successful installation, your node will begin synchronizing with the blockchain network. To monitor progress:

You will see synchronization details like this:

Wait for catching_up to turn false; indicating the sync is complete.

Complete the setup by executing the following:

Once this script completes, your node will be fully operational, and you will become a validator on the Kima Network blockchain.

From the Kima Backend

Using the Kima Backend, you can get the transaction status by calling two /tx endpoints depending on the type of transaction.

For regular transactions: GET /tx/:txId/status

For liquidity pool transactions: GET /tx/lp/:txId/status

Parameters:

• txId number: the transaction id number. This is a sequential number assigned to each transaction, NOT the transaction hash (tx_id below).

Success Response:

Example note: this sample response uses testnet-style token symbols such as USDK. If you are integrating against mainnet, expect the same response shape with supported mainnet symbols such as USDC.

Once the transaction has been submitted to the Kima Transaction Backend, you’ll want to display the transaction progress in the frontend. There are 2 GraphQL queries on the Kima subgraph for this purpose.

• Mainnet Kima Subgraph url: https://graphql.kima.network/v1/graphql

• Sardis Testnet url: https://graphql.sardis.kima.network/v1/graphql

Here is a code snippet for regular transactions using plain fetch. See the docs for your favorite graphql client for constructing queries.

Note: in the Kima subgraph, tx_id uses the GraphQL scalar bigint. In JSON variables, pass it as a numeric string such as "15519".

For liquidity pool transactions:

These are the current available transaction statuses returned from our blockchain and used throughout the SDK documentation today.

Introduction

Welcome to Kima Foundation (the “Foundation”). These Terms and Conditions (the “Terms”) govern your access to and use of our website (the “Website”) and any associated services provided by the Foundation (collectively, the “Services”). By accessing or using the Website or the Services, you agree to comply with and be bound by these Terms. If you do not agree with these Terms, you should not use the Website or Services.

Eligibility

You must be at least 18 years old to use our Services. By using the Website, you represent and warrant that you are of legal age to form a binding contract with the Foundation and meet all eligibility requirements. If you do not meet these requirements, you must not access or use the Website.

Use of Website and Services

Permitted Use

The Website and Services are provided solely for your personal, non-commercial use, and may not be used for any other purpose without our prior written consent.

Prohibited Activities

When using the Website and Services, you agree not to:

• Violate any applicable laws or regulations.

• Infringe on the rights of others, including intellectual property rights.

• Engage in any conduct that is fraudulent, abusive, or otherwise inappropriate.

• Introduce any viruses, malware, or other harmful software to the Website.

• Attempt to gain unauthorized access to any part of the Website, including any restricted areas or user accounts.

You may be required to register an account to access certain features of the Website. You agree to provide accurate and complete information during the registration process and to update such information as necessary. You are responsible for maintaining the confidentiality of your account credentials and for all activities that occur under your account.

All content, materials, and intellectual property available on the Website, including but not limited to text, graphics, logos, icons, and software, are owned by the Foundation or its licensors and are protected by copyright, trademark, and other applicable laws.

The Foundation grants you a limited, non-exclusive, non-transferable, and revocable license to access and use the Website and Services for personal, non-commercial use, in accordance with these Terms.

You may not modify, reproduce, distribute, create derivative works from, or otherwise exploit any content, materials, or intellectual property available on the Website without the Foundation’s prior written consent.

You may be permitted to submit or post content, such as comments or other materials, on the Website (“User-Generated Content”). You are solely responsible for the User-Generated Content you submit, and you represent and warrant that you have all necessary rights to do so.

By submitting User-Generated Content, you grant the Foundation a worldwide, non-exclusive, royalty-free, perpetual, and transferable license to use, reproduce, modify, adapt, publish, and display such content in any form, media, or technology now known or later developed.

The Foundation reserves the right to remove any User-Generated Content that violates these Terms or is otherwise objectionable, without prior notice.

Your privacy is important to us. Please review our Privacy Policy, which explains how we collect, use, and protect your personal information. By using the Website, you agree to the collection and use of your personal information in accordance with our Privacy Policy.

The Website and Services are provided on an “as-is” and “as available” basis, without any warranties of any kind, either express or implied. The Foundation disclaims all warranties, including but not limited to, implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

To the fullest extent permitted by applicable law, the Foundation shall not be liable for any direct, indirect, incidental, consequential, or punitive damages arising out of or in connection with your use of the Website or Services, even if the Foundation has been advised of the possibility of such damages.

You agree to indemnify, defend, and hold harmless the Foundation, its officers, directors, employees, agents, and affiliates from and against any and all claims, liabilities, damages, losses, and expenses, including reasonable attorneys’ fees, arising out of or in any way connected with your use of the Website or Services, or your violation of these Terms.

The Foundation reserves the right to suspend or terminate your access to the Website or Services at any time, for any reason, and without prior notice. Upon termination, all provisions of these Terms that by their nature should survive will continue to apply, including but not limited to, ownership provisions, warranty disclaimers, and limitations of liability.

These Terms shall be governed by and construed in accordance with the laws of Singapore, without regard to its conflict of law principles.

You agree to submit to the exclusive jurisdiction of the courts of Singapore for any disputes arising out of or relating to these Terms or your use of the Website or Services.

The Foundation reserves the right to modify these Terms at any time. Any changes will be effective immediately upon posting on the Website. Your continued use of the Website or Services following the posting of changes constitutes your acceptance of the revised Terms. It is your responsibility to review the Terms regularly.

If any provision of these Terms is found to be invalid or unenforceable, the remaining provisions will continue in full force and effect.

These Terms, along with our Privacy Policy, constitute the entire agreement between you and the Foundation with respect to your use of the Website and Services, and supersede any prior agreements or understandings.

If you have any questions about these Terms, please contact us at:

Kima Foundation 3 Fraser street #04-23a, Duo Tower, Singapore .

Because of the very specific nature of Kima's security model, explained in the validators intro and in the Kima White Paper, you need to ensure you meet the following hardware requirements before you become a Kima validator:

Must be an Intel XEON E-series or any other XEON supporting SGX-SPS (Server Platform Services). The motherboard must also support SGX.

• CPU: 4vCPU (8vCPU recommended)

• RAM: 16GB (32GB recommended)

• Storage: 512GB HDD (1TB recommended)

• Operating System: Ubuntu 22.04

Must be an Intel XEON E-series or any other XEON supporting SGX-SPS (Server Platform Services). The motherboard must also support SGX. The below list of supported SGX-compliant CPUs List is current for the second half of 2024

• Intel XEON E-2174G

• Intel XEON E-2176G

• Intel XEON E-2178G

• Intel XEON E-2186G

Credit Cards

Starting with version 1.4, Kima supports credit card transactions in the origin network (onramping)- off ramping to come in a future release. See Upgrading to v1.4.x for more information on how to upgrade your integration.

Credit card transactions require the use of the Kima Transaction Widget. This is a frontend React component which handles integration with Kima and 3rd party components which handle KYC and payment processing.

ℹ️ Check the list of unsupported Countries

Overview

The following steps outline the process of using the widget to buy stablecoins like USDC using a credit card.

1. From the "Source Network" dropdown, select "Credit Card"

1. From the "Target Network" dropdown, select the desired chain and token- i.e. USDT on Arbitrum

2. Fill in the wallet address (Target Address) and amount, then click "Next"

3. Choose where the service fees will be paid from and click "Next". There are 2 options. The difference is where the service will be paid from.

• In the first option, the service fees are paid upfront on the credit card. Choose this option to receive the exact amount you specified in the "Amount" field.

• In the second option, the service fees are deducted from the amount you will receive. So you will get slightly less stablecoins the amount you specified in the "Amount" field.

1. When you have confirmed all details, click Next. This will load the credit card provider screen.

From here there are couple differences between the Testnet and Mainnet versions of the widget.

1. Please skip the KYC process by pressing the "Approve KYC" button. KYC will be required in the Mainnet version.

1. Select the payment method. For now, the only payment method available is Credit Card. For testnet, please use fake information excpet for the card number.

• The expiration date must be in the future

• The CCV can be any number

1. In order to send a transaction users will need to perform KYC. Select your country and complete all steps needed to reach the next screen and fill in your information and credit card details.

Once you send all necessary data you'll need to wait a few minutes (or seconds) to proceed with the payment.

1. After the kyc process is complete, you'll be able to select your payment method. For now, the only available one is Credit Card:

In the next screen, fill in your card details and proceed with the payment:

If your transaction succeeds you will see the status screen, where you can track the current state of the transaction in the Kima blockchain.

If your payment is not sucessful, you will see a notification with a transaction id and asking you to contact support. Plese copy the transaction id and create a support ticket on the Kima Discord.

In this guide, you will learn how to delegate tokens to a validator using the Kima explorer.

Testnet explorer Mainnet explorer

Connect your wallet

From the left sidebar, select Validators.

Connect your wallet by clicking the Connect Keplr button on the top right corner.

Keplr will now prompt you to add the Kima network (mainnet or testnet) to your wallet's chain registry. To complete the operation, click the Approve button.

You should now see your Kima address instead of Connect Keplr in the top right corner.

View your KIMA tokens in Keplr

Keplr requires an extra step to display the KIMA network so you can view your tokens. From the extensions panel in Chrome, click on the Keplr extension and select the hamburger icon in the top left corner.

In the menu, select Settings.

On the next screen, select General.

Next, scroll down until you reach the Manage Chain Visibility button and click it.

This will open a new tab. In the search box, type kima for mainnet or kima-testnet for the testnet. and it should show the relevant network, along with your $KIMA tokens. Select it by clicking the checkbox and click Save.

You should now be able to see your $KIMA balance in your wallet.

Select one of the available validators in the Kima explorer and click on the Delegate button.

Enter the amount of $KIMA that you want to delegate. Ensure that you have sufficient balance for both the delegation amount and the fees for sending the transaction to the network. To confirm the delegation, click Submit.

You will now be prompted to approve the transaction. You will see the following information (numbers are examples):

• Method to execute: Stake

• Amount of tokens: 10 $KIMA

• Transaction fees: 0.05 $KIMA

Check all details, then click Approve and wait for the transaction to complete.

You should now see a success message, along with the transaction hash of the delegation.

To see further transaction details, you can click on the transaction hash, which will take you to the transaction details within the explorer.

There you can view details such as:

• Minimum period 30 days

• Minimum delegation >0

• Unbonding lockup period 7 days

• Commission fee X%

Finally you can see your delegated stake in the overview page of the explorer.

Ensure that the Kima network is operational and that there are no ongoing issues or outages.

Double-check the validator’s details before delegating to avoid any mistakes.

Make sure you have enough tokens to cover both the delegation amount and any associated network fees.

Below is a step by-step guide on how to deposit assets:

Step 0: Check you have enough funds

Before depositing liquidity, make sure:

• You have assets available for deposit.

• The assets are on the supported assets list.

• You have at least 0.2 Kima tokens in your Keplr wallet.

• You have enough funds for gas on your desired network (e.g., ETH for Ethereum, MATIC for Polygon, etc).

Browse to the Kima Explorer.

Browse to the Liquidity panel

Click the button in the upper right to connect your Keplr wallet

Your existing positions are now visible.

Select the blockchain you’d like to provide liquidity on.

Choose the amount you would like to deposit.

Select the asset you’d like to provide.

Click Deposit.

Upon clicking Deposit, a New Transfer window will appear. In this window:

Connect your blockchain wallet if you haven't already.

Review the transaction details, including the source network, wallet address, and deposit amount. Click Next.

After reviewing the transaction details, click Submit.

Approve all the transactions your wallets ask you to approve.

For all Kima Network transactions, you will be asked to make two approvals through your Keplr wallet.

Important: You may have to wait a few seconds for the second approval request to appear. If the Keplr wallet does not automatically launch, open it manually to see the pending approval requests.

Once you’ve signed and approved both requests, the transaction process will begin.

Once the transaction reaches 100% completion, your asset’s liquidity is deposited in the pool.

You can now view your balance, or withdraw it.

Drafting and submitting a proposal is a process that takes time, attention, and involves risk.

In an ideal world, a proposal should only fail to pass in a situation where engaged and aware make an informed decision to vote down the proposal.

If you are considering drafting a proposal, you should first review the general background on drafting and submission:

• How the voting process and governance mechanism works

• How to draft your proposal and engage with the Kima community about it

Add the widget to your React project using npm or your favorite JavaScript package manager.

You'll need to add the following:

• The <KimaProvider> component in App.tsx

• The <KimaTransactionWidget>

Web3 and crypto are currently at an inflection point which many technologies have failed to cross in the past. That is the main problem from which all the symptoms arise:

• Complicated experience: New users coming into crypto and Web3 are forced to quickly understand a slew of technically intensive terms and methods just to perform simple operations that are essential for using the new products this technology enables.

• Weak security: The current mechanisms and solutions are flawed. Despite blockchains being a superior solution for digital assets, blockchain-based are very vulnerable in transit between blockchain ecosystems. This is because these solutions are mostly built on technology incompatible with this purpose.

PLEASE READ THE ENTIRETY OF THIS "DISCLAIMER" SECTION CAREFULLY. NOTHING HEREIN CONSTITUTES LEGAL, FINANCIAL, BUSINESS OR TAX ADVICE AND YOU ARE STRONGLY ADVISED TO CONSULT YOUR OWN LEGAL, FINANCIAL, TAX OR OTHER PROFESSIONAL ADVISOR(S) BEFORE ENGAGING IN ANY ACTIVITY IN CONNECTION HEREWITH. NEITHER DIVERSIFI TECHNOLOGIES LTD (THE COMPANY), ANY OF THE PROJECT CONTRIBUTORS (THE KIMA TEAM) WHO HAVE WORKED ON KIMA (AS DEFINED HEREIN) OR PROJECT TO DEVELOP KIMA IN ANY WAY WHATSOEVER, ANY DISTRIBUTOR AND/OR VENDOR OF $KIMA TOKENS (OR SUCH OTHER RE-NAMED OR SUCCESSOR TICKER CODE OR NAME OF SUCH TOKENS) (THE DISTRIBUTOR), NOR ANY SERVICE PROVIDER SHALL BE LIABLE FOR ANY KIND OF DIRECT OR INDIRECT DAMAGE OR LOSS WHATSOEVER WHICH YOU MAY SUFFER IN CONNECTION WITH ACCESSING THE PAPER, DECK OR MATERIAL RELATING TO $KIMA (THE TOKEN DOCUMENTATION) AVAILABLE ON THE WEBSITE AT HTTPS://WWW.KIMA.NETWORK/ (THE WEBSITE, INCLUDING ANY SUB-DOMAINS THEREON) OR ANY OTHER WEBSITES OR MATERIALS PUBLISHED OR COMMUNICATED BY THE COMPANY OR ITS REPRESENTATIVES FROM TIME TO TIME.

This document is created by Kima for educational and informational purposes only. The contents of this document are not a financial promotion. None of the information or analyses presented are intended to form the basis for any investment decision and no specific recommendations are intended. Therefore, none of the contents of this document serve as an invitation or inducement to engage in any sort of investment activity. This document is not intended to be a prospectus, solicitation, inducement or oering for investment or the sale or issuance of securities or any interests or assets.

By accessing the Token Documentation or the Website (or any part thereof), you shall be deemed to represent and warrant to the Company, the Distributor, their respective affiliates, and the Kima team as follows:

(a) in any decision to acquire any $KIMA, you have not relied and shall not rely on any statement set out in the Token Documentation or the Website;

Before you can start providing liquidity to Kima Finance pools, you will need to set up wallets for interacting with the Kima protocol, and the supported target blockchains.

Kima is a Cosmos based blockchain. To interact with Kima, you need to:

• Install a Cosmos wallet such as Keplr.

• Download your wallet

The following information is needed to prepare for and ultimately submit a Kima transaction.

• The fee amount and feeId

• The user choice of whether to pay fees from the origin or target chain

• The message containing the transaction details for the user to sign

• The origin token amount the user must authorize so Kima can move tokens on behalf of the user

• The amounts expected when the transaction is submitted

Fortunately, all of these values are calculated by an endpoint exposed by the Kima chain.

Using this endpoint is required as it will return a feeId which must be passed to submit endpoints in the backend (/submit/transfer or /submit/swap).

• Non-BTC origin transactions submitted to Kima without a feeId or signature will be rejected

• For non-BTC origin transactions, submitted amounts are validated against the feeId and signed message. Any mismatch will result in rejection.

These are security measures to protect the user and ensure the transaction is legitimate.

Use GET /chains to read token metadata for the selected origin token.

• decimals: use this for amount handling

• isPermit2: determines whether submit payload must include options.permit2

For BTC-origin transactions, GET /submit/fees is still required to get feeId and the submit amount.

Before calling /submit/transfer or /submit/swap, prepare BTC HTLC lock data:

1. POST /btc/htlc/lock-intent

2. User broadcasts BTC to the returned htlcAddress

3. POST /btc/htlc/record using the broadcast txid

The values returned by /btc/htlc/record are then included in the final submit payload.

GET /submit/fees

Query Params (all required):

• amount (number): the amount of tokens to transfer

• originAddress (string): the source user address

• originChain (string): the chain the user tokens will come from

Example:

Port note: these direct backend examples use the backend's default local port 3001. If your frontend or local proxy exposes the backend on another port such as 4000, use that URL instead.

Example note: this sample uses USDK, which is a testnet token. If you are integrating against mainnet, replace it with a supported mainnet token such as USDC.

Success Response:

Amounts are returned as both numbers representing the amount in whole tokens and as a string representing the integer amount in the smallest unit of the token (e.g. USDC is 6 decimals).

• feeId (string): a unique identifier for the fee; include this in submit requests

• feeOrigin* the gas fee for the origin chain

• feeKimaProcessing* The processing fee (currently 0.05%)

The response field is still named allowanceAmount, but treat it as the origin token authorization amount. There are 2 variants returned depending on whether the user chooses to pay fees from the origin or target amount.

• When paying fees from the origin, use transactionValues.feeFromOrigin values.

• When paying fees from the target, use transactionValues.feeFromTarget.

Example:

Transferring 10 USDK from ARB to SOL with 0.07371 USD in total fees.

When paying fees from the origin

• The user pays fees on Arbitrum. The total fees are included in the authorization amount.

• User signs the message I approve the transfer of 10.07371 USDK from ARB to <targetAddress> on SOL. (feeFromOrigin.message)

• The authorization amount is 10.07371 USDK (feeFromOrigin.allowanceAmount

When paying fees from the target chain

• The user does not pay fees on Arbitrum

• User signs the message I approve the transfer of 10 USDK from ARB to <targetAddress> on SOL. (feeFromTarget.message)

• The authorization amount is 10 USDK (feeFromTarget.allowanceAmount)

Save the corresponding submitAmount, message and feeId for later as they are needed to submit the transaction.

If you need the raw fee-calculation API instead of the backend wrapper, the backend currently calls the fee service at POST {{baseUrl}}/v3/fees/calculate. For most integrations, GET /submit/fees remains the recommended entry point.

Major Features

• Bank transfers as an origin rail (e.g. SEPA → on-ramp to crypto).

• Unified “FIAT rails” handling (BANK and CC) in the submit flow.

• On-chain stable token swaps via a new /submit/swap endpoint.

• Safer, stricter “options” contract between frontend, backend and the blockchain for FIAT rails.

UPGRADING TO v1.5.x IS REQUIRED FOR ALL KIMA SDK USERS. Older payloads will fail once 1.5 validators/submit rules are enforced.

• Origin rails BANK and CC are now treated as FIAT internally when we submit to Kima Chain.

• Backend normalizes:

  • originChain: 'CC' | 'BANK' → 'FIAT'

• Swaps are submitted through POST /submit/swap with:

• amountIn, amountOut, fee (all bigint strings),

• decimals

• Backend must submit options as a JSON string. (Objects are not accepted by the API.)

• For crypto → crypto:

  • include feeId (from fee estimator),

  • include the signed user approval.

Install the latest version of the .

Notes

• No new required props for 1.5.x specifically, but if you want to pass a custom Solana RPC, the widget provider accepts solRPC (optional).

• Existing network filters remain backend-driven (no re-introducing removed props).

Navigate to the repo and and pull the latest version.

• If origin is FIAT (BANK/CC):

• Accept a fiatTransactionIdSeed in the body (or options.transactionIdSeed).

• Call your existing helper to generate FIAT options (it must preserve the seed and add transactionIdSignature).

Minimal example (server side):

Common FIAT options keys you’ll be sending:

• feeId — required (from the fee estimator)

• paymentMethod — e.g. "sepaEur" for BANK and "creditCard" for CC

• chargeFeeAtTarget

• Uses amountIn / amountOut (bigint strings).

• FIAT rules apply when origin is BANK/CC (transactionIdSeed + signature, origin normalized to FIAT, empty address).

• As in 1.4, you must call the fee estimator before submit.

• 1.5 continues to use feeId in the subsequent submit request (transfer or swap).

• GET /submit/transactionId?transactionIdSeed=<uuid> — returns encoded transactionId (for CC flows). (Your FIAT helper already calls the underlying logic that also produces transactionIdSignature.)

• Upgrade widget to latest @kimafinance/kima-transaction-widget.

• Backend:

  • Ensure /submit/transfer preserves transactionIdSeed in options and adds transactionIdSignature

Once a proposal is on-chain, it cannot be changed to reflect feedback or new information. It is very important to give a proposal time off-chain to receive feedback, input, and edits before going on-chain and asking for votes.

The process of passing a proposal starts long before it goes on-chain!

There are currently several types of proposals supported by Kima:

• Text: Proposal to agree to a certain strategy, plan, commitment, future upgrade or other statement. Text proposals do not directly cause any changes, but they can be used to take a record of the community's opinion or commitment to a future idea.

• Community Pool Spend: Proposal to spend funds from the community pool on a project