Skip to main content
This page takes you from zero to a cross-network swap sourced from Kaia. No new contracts, no approval for native KAIA, one signed transaction for your user.
Building with an AI assistant? Add the SODAX Builders MCP (https://builders.sodax.com/mcp) to Claude, Cursor, or any MCP-capable tool and it can pull live token lists, real quotes, and these docs while it writes your integration.

1. Install

2. Create a Kaia wallet provider

Kaia uses the same EvmWalletProvider as every other EVM network, keyed by ChainKeys.KAIA_MAINNET. The account behind it must have Kaia’s AccountKeyLegacy key type. Kaia creates accounts with that type, and it stays until the owner updates the key.
Building in React? @sodax/wallet-sdk-react connects EVM wallets for you and hands back a ready-made provider via useWalletProvider. See Wallets.

3. Look up supported tokens

Token addresses and decimals come from the SDK config, so you never hard-code them.

4. Quote and swap

swap() runs the full lifecycle: it creates the intent on Kaia, verifies the transaction landed, relays it to the hub, and notifies the solver to fill on the destination network.
ok means the intent was created, relayed to the hub, and the solver notified, not that it was filled. Poll sodax.swaps.getStatus({ intent_tx_hash: intentDeliveryInfo.dstTxHash }) until the status is SolverIntentStatusCode.SOLVED, which is the only success signal. The main quickstart has the full polling loop, including why NOT_FOUND is not terminal. A few things to know on Kaia:
  • KAIA needs no approval. It is the native token. Swapping an ERC-20 token on Kaia needs an allowance first; see Approvals.
  • Amounts follow token.decimals. KAIA has 18 decimals, but not every Kaia token does: USDT on Kaia has 6. Always build amounts from the token’s own decimals.

Next steps