Skip to main content

Do I need to write or deploy a contract?

No. SODAX’s Kaia spoke contracts are already deployed; your integration is TypeScript against @sodax/sdk (or the React packages on top of it). You write no on-chain code and hold no admin key for any part of the flow.

How does a swap from Kaia actually settle?

Your user signs one EVM transaction on Kaia that creates an intent. The SODAX relayer carries proof of that transaction to the hub network (Sonic), a solver fills the intent on the destination network, and the output lands at the recipient address there. If an intent is never filled, it can be cancelled and the funds recovered.

Which assets are supported on Kaia?

Two answers, and the difference matters. On Kaia itself, 4 assets are live for swaps, and 4 work in the money market, with native KAIA among them today. But your users are not limited to the Kaia-side list. Every swap is cross-network, so from Kaia they can reach all 166 assets across every SODAX-supported network. Both lists grow as the backend config adds them; see the live tables in Networks & Assets.

Can an account with an updated or multisig key use SODAX?

Not from that account. SODAX and EVM wallets send Ethereum-format transactions, and Kaia only accepts those from accounts with the AccountKeyLegacy key type, whose address is derived from their key. An account that switched to a different key, a multisig key, or role-based keys can still hold KAIA and tokens, but cannot sign the transaction that creates an intent. See Kaia accounts.

Does SODAX use Kaia’s fee delegation?

No. Fee delegation is a set of Kaia-specific transaction types, and SODAX sends standard Ethereum-format transactions. The user’s account pays its own gas in KAIA.

Is there an approve step before swapping or supplying?

For ERC-20 tokens, yes. isAllowanceValid checks the allowance and approve sets it, the same as on any EVM network. Native KAIA needs no approval.

Which RPC endpoint should I use?

Your own, in production. The SODAX config uses Kaia’s public endpoint, https://public-en.node.kaia.io, which Kaia provides for testing and development and asks not to be used commercially. Its list of public endpoints also names node providers. Pass your endpoint through rpcUrl on EvmWalletProvider, or per chain in the @sodax/wallet-sdk-react config.

Is there a testnet?

No. SODAX is mainnet-only on every network, Kaia included.

What does it cost?

Using SODAX is free: no license, no integration fee, no SDK cost. Trades carry a fixed 0.1% base fee taken by the protocol; on top of that you set your own platform fee and keep it. Your users also pay Kaia’s network fees in KAIA. See Monetize SDK.

How do I know if something went wrong?

SDK operations return Result<T> rather than throwing. Core swap and money market methods return typed error codes (for example 'RELAY_TIMEOUT', 'EXECUTION_FAILED') you can branch on, with structured context attached.

Where are the audits?

Audits for the SODAX protocol are collected on the Audits page.

Can my AI coding assistant do the integration?

Largely, yes. Add the SODAX Builders MCP to Claude, Cursor, VS Code, Windsurf, or any MCP-capable client (https://builders.sodax.com/mcp) and it gets live access to the SODAX System: chains, tokens, swap quotes, money market rates, intent history, and auto-synced SDK docs. Use it to scope the integration against your own codebase first, then to write and verify the code. Setup per client is at builders.sodax.com.

I want a plan specific to my protocol. Who do I talk to?

Reach the SODAX team through any platform listed at linktr.ee/go.sodax.