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.

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.

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, currently available for the Kima Devnet, is an essential dashboard showing all the key facts about the state of the network, including transaction history.

If you are developing on Kima, this is where you will be able to monitor your transactions.

@ -1,35 +0,0 @@

The Kima Light Demo App

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.

Try the light demo

Select Source Network

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.

Select Target Network

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

Enter Amount

Type the amount of USDK you want to transfer.

Confirm Details

A summary screen shows:

• Source and target chains

• Wallet addresses

• Transfer amount

• Network and liquidity fees

Review everything, then submit the transaction.

Once you have submitted the transaction, you can watch it complete in real-time by clicking the transaction links to the block explorers that are involved.

ℹ️ 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.

Payment methods

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

Supported currencies

• US Dollar

• EURO

ℹ️ Other currencies coming soon.

Unsupported countries - credit cards

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.

Unsupported Credit Cards

The following credit cards are currently not accpeted:

• American Express

ℹ️ Support for additional credit cards coming soon.

1. If you haven't already,

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

3. Connect your Keplr wallet

4. Filter to "Kima" and add Kima Mainnet (and Testnet) - this adds the 2 blockchains to your wallet

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.

Challenges in Blockchain Interoperability

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.

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.

Genesis File Governance Parameters

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.

Governance parameters​

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

• Minimum deposit: 10,000 KIMA

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.

Modes

The Kima Transaction Widget supports 3 modes:

1. Payment

Overview

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

Getting Started

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 .

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:

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 endpoint.

Message Structure

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

• Allowance amount: in whole tokens i.e.

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> which interacts with Kima

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 Avalance.

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 .

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 the /submit endpoint- not the transaction hash. I.e 22843

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.

How to configure access to blockchain networks with a managed service

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

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.

Troubleshooting

There is an extra step that needs to happen if you are using Kima's tools to transfer to or from Solana wallets. The recipient wallet first needs to be "primed" by sending a small amount of USDK to the wallet before transfers or payments via Kima can take place.

This applies to the testnet only and will not be the case once Kima's mainnet goes live.

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

White Paper

Tech Paper

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

• Bera 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 .

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 .

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.

Instructions for USDK faucet - Solana and Tron

To acquire testnet USDK on Solana or Tron, the process is broadly the same but you will need to use a wallet that is compatibile 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.

USDK faucet - Solana

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.

USDK faucet - Tron

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.

Instructions for KIMA faucet

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.

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 (recommended), and .

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.

Adding funds to your wallet

Using a faucet

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.)

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.

Earn Network Fees

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).

Capital Efficiency

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

Cross-chain 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.

Security

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.

Conclusion

Kima Finance’s liquidity pool system is designed to be efficient, secure, and flexible. Liquidity providers can benefit from participating in cross-chain pools, earning rewards through network fees and bounties. For more information on becoming a liquidity provider, refer to the section.

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.

Step 2: Initiate the withdrawal process

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

Step 3: Confirm Transaction in the New Transfer Window

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.

Step 4: Approve the transaction

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.

Step 5: Sign approval requests in Keplr

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.

Step 6: Verify the Withdrawal

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.

Using Kima SDK without the widget

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. But:

🚨 CREDIT CARD TRANSACTIONS ARE ONLY SUPPORTED USING THE WIDGET 🚨

The frontend kima-transaction-widget is required as it must handle KYC and interactions with 3rd party widgets.

Transaction Flow

1. User selects the origin and target chains and amount

2. Fetch the service fees from Kima to obtain a feeId

3. User signs a message containing the transaction details

4. User approves Kima to transfer the origin tokens on their behalf

Reference Implementation

The React component on the Kima Github:

Selecting Chains and Amount

The frontend component will need to provide the following information. This will be used to calculate the service fee and the approval for Kima to move tokens on behalf of the user.

• Origin (from)

  • chain: this is the chain the user tokens will come from

  • token: the (stable coin) token the user will pay with (or bridge from)

  • address: the source user address- i.e. the connected user

Supported Chains and Tokens

See the list of chains and tokens in the section.

Bank Transfers

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

Bank transfer transactions require the use of the Kima Transaction Widget. This is a frontend React component which handles integreation 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 EURC using a bank account.

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

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

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 bank transfer. 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 bank transfer provider screen.

Testnet Version

6.1. Currently, there is no way to do a bank transfer in "test mode" since our fiat provider expects to receive an actual bank transfer to trigger the logic behind it.

Mainnet Version

6.2. 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 personal information.

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, the widget will display the bank account details that you must transfer the assets to.

Once you're ready, click on the finish button. This will send the needed transaction request to the kima blockchain. From there, you can track the current state of the transaction in the Kima blockchain.

If your transaction succeeds you will see a success screen. You can go back in this step, and check all details regarding the transaction.

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.

Bridging

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.

First, we connect our wallet, ensuring we are on the network from which we wish to send funds.

The widget pre-fills the target address field with the same wallet address we are sending from (if both network addresses are the same type), but this can be changed to a different address if desired.

We approve the transaction in our wallet...

... and then in the next step submit it.

We can follow the transaction status in the next screen, and check completion in each network explorer by selecting the corresponding transaction hashes.

If we wish, we can also retrieve the proper transaction id to follow the status of the transaction later.

Once the transaction is found, the status will be displayed with its corresponding state and transfers.

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 chain and token supported by Kima. The funds will be transferred to the wallet and chain specified in the transactionOption prop

• The title and subtile can be customized using the titleOption and paymentTitleOption props

⚠️ On testnet, transactionOption.currency must be USDK as this is the only currency supported on testnet. You will need to switch the currency based on whether your app is currently using testnet or mainnet.

You should see a page that looks like this:

The payment (target) wallet and chain will show on the next step when the user approves the transfer amount.

Once the user sends the approval and submits the transaction, the user can see the transaction status in the next step.

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

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.

Upgrading to v1.4.x

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.

Scope of the Policy

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.

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 and are the same when using testnet. 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.

Testnet support

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

Querying for Supported Chains

For an up to date list of support chains query the following endpoint:

GET

Params

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

Reponse

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

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.

Interacting with Kima

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

• Install a Cosmos wallet such as Keplr.

• Download your wallet

Follow the instructions to create a new wallet. Secure your seed phrase!

Add the Kima blockchain to the wallet.

Go to the :

Browse to the Liquidity panel

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

Accept all the parameters that will add Kima Mainnet chain to your wallet

You will need Kima tokens to pay gas for the provisioning operations.

Supported Networks and Wallets

Kima offers broad support for multiple blockchain networks, allowing you to connect using a variety of wallets compatible with WalletConnect. You are not limited to specific wallets; instead, you can choose from options such as:

• EVM-compatible blockchains: To provide liquidity on any EVM-compatible blockchain (Ethereum, Arbitrum, BNB, etc.) use any EVM-compatible wallet such as MetaMask.

• Solana: To provide liquidity on Solana, use Solflare, Phantom, or any other Solana-compatible wallet.

• Tron: We have provided instructions for TronLink.

• Bitcoin: We have provided instructions for XVerse.

Below are the setup instructions for each wallet option:

EVM-compatible blockchains

For EVM-compatible blockchains, such as Ethereum, Polygon, or Optimism, you may use a wallet such as MetaMask.

Install MetaMask: Download MetaMask as a browser extension or mobile app from the MetaMask website.

Create a wallet: Follow the prompts to create a wallet. Secure your seed phrase!

Add blockchains: Add the blockchains you’d like to provide liquidity on to your MetaMask wallet.

The easiest way is to browse to and add the desired blockchains.

See the section for a list of supported chains.

Solana

For interacting with Kima's liquidity pools on Solana, you may use Solflare or a similar wallet that supports Solana.

Install Solflare: Download the Solflare wallet from the Solflare website.

Create a Wallet: Set up your Solflare wallet. Secure your seed phrase!

Tron

For interacting with Kima's liquidity pools on Tron, you may use TronLink or a similar wallet that supports Tron.

Install TronLink: Download TronLink from the TronLink website.

Create a Wallet: Follow the instructions to create your Tron wallet. Secure your seed phrase!

Bitcoin

To provide liquidity to the Kima Finance Bitcoin pool, you may use XVerse wallet, a recommended wallet for interacting with Bitcoin.

How to Set Up XVerse Wallet:

Install XVerse: Download the XVerse wallet from the XVerse website.

Create a Wallet: Follow the prompts to set up your XVerse wallet. Secure your seed phrase!

You are now ready to start providing liquidity to Kima pools across various networks. If you encounter any issues during setup, refer to the official documentation of each wallet or reach out to the Kimae community for support.

Instructions for using these wallets do not represent an endorsement by Kima of any of the wallets mentioned.

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

npm install @kimafinance/kima-transaction-widget redux react-redux pino-pretty

You'll need to add the following:

• The <KimaProvider> component in App.tsx

• The <KimaTransactionWidget> which interacts with Kima

• A link to the Kima Transaction Backend (or build your own)

• A WalletConnect project id

For the purposes of this example, we'll just add the widget to App.tsx, but it can go anywhere it makes sense for your project.

Open App.tsx, wrap your existing componts with the <KimaProvider> and add the <KimaTransactionWidget> component.

If you don't have one already, you'll need to get a (free) WallectConnect project ID from and add it to the <KimaProvider> component.

There are several configuration options, which will described in the section on setting up the widget.

Polyfills

Note that if you are using a later version of webpack (>= 5), you will need to polyfill node core modules using react-app-rewired.

This can be resolved by adding a file at the root of your project named config-overrides.js. Paste the following content into the file:

Example

The easiest way to see the widget working, including the polyfill workaround, is to check out .

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

SGX requirements

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

Compliant servers

• Intel XEON E-2174G

• Intel XEON E-2176G

• Intel XEON E-2178G

• Intel XEON E-2186G

Compliant servers

The procedure for adding the Kima Transaction Widget to a NextJS app is very similar to the React tutorial but you should be aware that you will need to export the widget component as a dynamic component with {ssr: false} so that the application runs the widget on the client side.

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

You'll need to add the following:

• The <KimaProvider> component in App.tsx

• The <KimaTransactionWidget> which interacts with Kima

• A link to the Kima Transaction Backend (or build your own)

• A WalletConnect project id

If you don't have one already, you'll need to get a (free) WallectConnect project ID from and add it to the <KimaProvider walletConnectProjectId='your-project-id' /> component.

Within your app directory, create a components directory and inside that create a file named widget.jsx with the following code:

Copy

You can now use DynamicApp on whatever page you like. In our example, we will create an index page index.jsx in our pages directory and copy the following code:

Copy

When you visit localhost:3000 you will see something like this:

See the section for more details on setting up the widget.

Troubleshooting

Turbopack (Development)

The widget is not currently compatible with the --turbopack flag. Please disable this flag when running the development server.

Why do we need Kima?

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.

• Expensive compliance: International financial regulations exist to protect consumers. But for the innovators building the future of finance, protection took a back seat to inclusivity and progress. This made compliance an expensive patch instead of an integrated solution.

Who is it for?

Anyone can use Kima’s SDK to add functionalities to their dApps using Kima’s settlement layer, and thanks to its novel approach to infrastructure design, maximum security is already built into the platform, with opt-in compliance allowing dApps to expand into the preexisting monetary system and vice-versa.

• dApp builders use Kima to onboard users from any chain or no chain at all, and let Kima handle the technical or security implications, allowing builders to focus on providing a better product for more users.

• Institutions wishing to implemnt Web3s use Kima to extend their solutions to additional chains without spending resources on compliance or technological feasibility,

• Web2 developers use Kima’s payment functionality to easily integrate web3 solutions into their existing products, joining the next evolution of the world wide web.

What does it do?

Kima enables transfers of assets between different blockchain networks and bank accounts, using a purpose-specific chain that transacts directly with the source and target blockchains/banks. This means that sensitive funds are secured in transit and are not kept on experimental technologies prone to exploits such as smart contracts, but rather on tested solutions - such as TSS and SGX - that have endured the rigours of real-world use.

What are some typical Kima use cases?

Kima solves the problem in any situation where funds need to be sent seamlessly from one network to another without the user having to exit the application and go elsewhere to bridge funds. For example, a user may have funds on Ethereum but want to purchase from an eCommerce site which uses Polygon or Avalanche, or to add liquidity to a liquidity pool on a different chain. Removing the friction from the payment or bridging process and enabling a simple in-app experience is crucial to onboarding more users to the Web3 ecosystem. See Use Cases for a fuller description of all the things you can do with Kima.

How does it work?

Kima takes a simpler approach to settlement security: If it’s not there it can’t be hacked. This means no smart contracts, no oracles, no external relayers to trust that can be compromised. So how are funds moved without smart contracts? The technical solution is comprised of three parts:

External accounts EOAs (Externally Owned Accounts) are native blockchain wallets acting as pools. The security benefits of this are immense: No need for smart contracts on every blockchain, You can’t DDoS a wallet, and everything related to cross-contract messaging is non-existent so this is not an applicable attack surface.

TSS and Trusted execution environments Using TSS and Intel SGX technology, keys are shared between different actors without them having direct access to these keys. This means we can allow more people to run these nodes and not be worried about keys being compromised.

Efficient Liquidity management High TVL numbers only tell part of the story. Liquidity protocols need to balance between the liquidity pools to ensure a high service level. In other words, it’s not only about how much money is stored, it’s also about distributing the liquidity in a way that will serve demand in the most effective way. Kima’s Liquidity Management (LiMa) algorithm manages supply and demand and maintains equilibrium using financial incentives.

Fiat Support To allow for integration between the old and new monetary systems, Kima also employs an opt-in compliance system on the protocol level, allowing decentralized solutions access to legacy systems like Fiat payments, Stocks and Bonds. This layer will perform all the necessary checks, including KYC, AML and KYT verifications to provide a compliant record that satisfies regulatory requirements.

Anyone building in Web3 can see the challenges that Web3 compatibility brings. Instead of perceiving these challenges as independent problems with no relation to each other, Kima understands that these are symptoms of the same problem.

Kima’s solution is the first compatibility layer that solves the problem, instead of treating the various symptoms that arise from it.

Where can I see Kima working?

You can see the Kima Demo App and read about how to use it .

Which networks does Kima support?

See the current list of supported networks .

Where can I read more about Kima?

You can find the Kima Whitepaper .

How can I become a validator?

We have quick-start instructions for installing a validator node in .

In what front end frameworks can I use the Kima Transaction Widget

The widget can be embedded into any React application, including NextJS. We do not currently support Vue or Angular applications. However, regardless of the framework you are using, you will be able to use the Kima back end and integrate your front end that way instead. Read the instructions .

Mainnet

• USDC

• USDT

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.

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

Connect your wallet

From the left sidebar, select Validators.

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

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.

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.

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:

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;

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 containting the transaction details for the user to sign

• The allowance amount the user should approve 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 the /submit endpoint in the backend.

• Transactions submitted to Kima without a feeId or signature will be rejected

• Submitted amounts will be validated against the feeId and signed message. Any mismatch will result in the transaction being rejected.

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

Using the Kima Backend

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:

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 the /submit request

• feeOrigin* the gas fee for the origin chain

• feeKimaProcessing* The processing fee (currently 0.05%)

The allowanceAmount is the one you'll need to pass to the contract call. 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 USDC 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 allowance amount.

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

• The user approves a transfer of 10.07371 USDC on Arbitrum (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 user approves a transfer of 10 USDC on Arbitrum (feeFromTarget.allowanceAmount)

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

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 integreation 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.

Testnet Version

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.

Testing Cards

• The expiration date must be in the future

• The CCV can be any number

Mainnet Version

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.

Once the user has signed the message and approved the token transfer, it’s time to construct the submit request to the Kima Transaction Backend. Use transactionValues returned by the /submit/fees endpoint.

Again, like for the message signing, the select the appropriate version based on whether the user is paying fees from the origin or target chain.

• If the user is paying fees from the origin, use transactionValues.feeFromOrigin.submitAmount.

• If the user is paying fees from the target, use transactionValues.feeFromTarget.submitAmount.

Submitting the Transaction

POST /submit Request Body:

• originAddress (Address): sending user address

• originChain (string): sending chain

• originSymbol (string): sending token symbol

See the list of chain short names in the section.

Make sure the decimals for the bigint amounts are all the same. You may need to convert the value for feeTotalBigint to the same decimals as the submitAmount before passing it to the backend.

Success Response:

• height: number

• txIndex: number

• code: number: error code; will be zero when successful

Get Transaction Id

The transaction Id will be needed to fetch the transaction status. The following code can be used to extract the Id from the submit response.

Validation

If provided, the Kima Backend will use the url defined in the ENV var COMPLIANCE_URL to get the risk score for the origin and target user addresses. If the score is anything other than low it will respond with a 500 error.

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

• How to format proposals

• How to submit your proposal

You should also review details specific to each kind of proposal, listed in this section.

Text (Signaling)

What are signaling proposals currently used for?​

Signaling proposals are used to make an on-chain record of support or agreement on a certain topic or ideas. Text proposals do not contain any code. In other words, they do not directly cause any changes to the Hub if they are passed.

Past signaling proposals have been used for a variety of reasons:

• Agreement to adopt (or not adopt) a feature in a future release

• A high-signal alert to validators

• On-chain record of community opinion

• Ratification of a social norm

Why make a signaling proposal?​

Signaling proposals are a great way to take an official public poll of community sentiment before investing more resources into a project. The most common use of text proposals is to confirm that the community is actually interested in what the proposer wants to develop, without asking for money to fund development that might not be concrete enough to have a budget yet.

Because the results of signaling proposals remain on-chain and are easily accessible to anyone, they are also a good way to formalize community opinions. Information contained in documentation or GitHub repos can be hard to find for new community members but signaling proposals in a block explorer or wallet is very accessible.

You might make a signaling proposal to gather opinions for work you want to do for the Hub, or because you think it is important to have a record of some perspective held by the community at large.

What happens when a signaling proposal passes?​

Technically, nothing happens on-chain. No code executes, and this 'unenforceable' property of text proposals is one of the biggest criticisms of the format. Regardless of whether the results of a signaling proposal are enforced by code, there can still be value from having a proposal on-chain and subject to discussion. Whether a proposal passes or fails, we all get information from it having been considered.

• The community might have had a thorough, thoughtful discussion about a topic that they otherwise would not have had.

• A development team interested in a feature might have a better idea of how their work will be received by the community.

• The community might be more informed about a topic.

• The community might feel confident that we are aligned on a particular definition or social norm.

Submitting a text proposal​

Follow the instructions below to create a text proposal and submit it to the network.

Community Pool Spend

Unlocks the potential for token-holders to vote to approve spending from the Community Pool.

Learn About the Community Pool​

How is the Community Pool funded?​

2% of all staking rewards generated (via block rewards & transaction fees) are continually transferred to and accrue within the Community Pool. For example, from December 19, 2019 until January 20, 2020 (32 days), 28,726 ATOM were generated and added to the pool.

How can funding for the Community Pool change?​

Though the rate of funding is currently fixed at 2% of staking rewards, the effective rate is dependent upon Kima staking rewards, which can change with inflation and block times. The current parameter Community Tax parameter of 2% may be modified with a governance proposal and enacted immediately after the proposal passes.

How much money is in the Community Pool?​

You may directly query Kima for the balance of the Community Pool:

Alternatively, the Kima Explorer will display the ongoing Community Pool balance.

How can funds from the Community Pool be spent?​

Funds from the Kima Community Pool may be spent via a successful governance proposal.

How should funds from the Community Pool be spent?​

We don't know 🤷

The prevailing assumption is that funds should be spent in a way that brings value to Kima. However, there is debate about how to keep the fund sustainable. There is also some debate about who should receive funding. For example, part of the community believes that the funds should only be used for those who need funding most. Other topics of concern include:

• Retroactive grants

• Price negotiation

• Fund disbursal (eg. payments in stages; payments pegged to reduce volatility)

• Radical overhaul of how the community-spend mechanism functions

We can expect this to take shape as proposals are discussed, accepted, and rejected by the Kima community.

How are funds disbursed after a community-spend proposal is passed?​

If a community-spend proposal passes successfully, the number of $KIMA encoded in the proposal will be transferred from the community pool to the address encoded in the proposal, and this will happen immediately after the voting period ends.

Why create a proposal to use Community Pool funds?​

As a strategy: funding is fast. Besides the time it takes to push your proposal on-chain, the only other limiting factor is a fixed 14-day voting period. As soon as the proposal passes, your account will be credited the full amount of your proposal request.

To build rapport. Engaging publicly with the community is the opportunity to develop relationships with stakeholders and to educate them about the importance of your work. Unforeseen partnerships could arise, and overall the community may value your work more if they are involved as stakeholders.

To be more independent. The Interchain Foundation (ICF) may not always be able to fund work. Having a more consistently funded source and having a report with its stakeholders means you can use your rapport to have confidence in your ability to secure funding without having to be dependent upon the ICF alone

Parameter change

Drafting and submitting a parameter-change governance proposal involves two kinds of risk: losing proposal deposit amounts and the potential to alter the function of the Kima network in an undesirable way.

What parameters can be changed?​

The complete parameters of the Kima network are split up into different modules, each of which has its own set of parameters. Most parameters can be updated by submitting a governance proposal.

List of modules whose parameters can be changed via governance:

x/auth x/bank x/distribution x/evidence x/feegrant x/gov x/mint x/slashing x/staking ibc-go/transfer interchain-security/provider Each cosmos-sdk module uses MsgUpdateParams for providing parameter changes. You can learn more about it in the cosmos-sdk documentation of each module, for example

What are the current parameter values?​

There are ways to query the current settings for each module's parameter(s). Some can be queried with the command line program gaiad. You can begin by using the command gaiad q [module] -h to get help about the subcommands for the module you want to query. For example, gaiad q staking params returns the settings of relevant parameters:

bond_denom: uKIMA max_entries: 7 max_validators: 180 unbonding_time: 1814400s

If a parameter change proposal is successful, the change takes effect immediately upon completion of the voting period.

Note: You cannot currently query the bank module's parameter, which is sendenabled. You also cannot query the crisis module's parameters.

Why create a parameter change proposal?​

Parameters govern many aspects of Kima's behaviour. As circumstances and attitudes change, sometimes you might want to change a parameter to bring the chain's behaviour in line with community opinion. For example, the Cosmos Hub launched with 100 active validators and there have been 4 proposals to date that have increased the MaxValidators parameter. At the time of writing, the active set contains 180 validators.

The Cosmos Hub has been viewed as a slow-moving, highly secure chain and that is reflected in some of its other parameters, such as a 21 day unbonding period and 14 day voting period. These are quite long compared to other chains in the Cosmos Ecosystem

Risks in parameter change proposals​

Because parameters dictate some of the ways in which the chain operates, changing them can have an impact beyond what is immediately obvious.

For example, reducing the unbonding period might seem like the only effect is in how quickly delegators can liquidate their assets. It might also have a much greater impact on the overall security of the network that would be hard to realize at first glance.

This is one of the reasons that having a thorough discussion before going on-chain is so important - talking through the impacts of a proposal is a great way to avoid unintended effects.

Software Upgrade

Use the draft-proposal command to create a draft proposal and populate it with required information.

Configuration options

Configure the widget's look and feel

There are numerous ways to configure the Widget for your own preferences and the look and feel of your dApp, which you can do via the following props:

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.