Skip to main content
This page takes you from zero to a cross-network swap sourced from Ethereum. No new contracts, no approval for native ETH, 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 an Ethereum wallet provider

Ethereum uses the same EvmWalletProvider as every other EVM network, keyed by ChainKeys.ETHEREUM_MAINNET.
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 Ethereum, 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 Ethereum:
  • ETH needs no approval. It is the native token. Swapping an ERC-20 (USDC, USDT, bnUSD, and the rest) needs an allowance first; see Approvals.
  • USDT may ask for two signatures. If the wallet already holds a stale USDT allowance, approve resets it to zero before approving the new amount. See USDT approvals.
  • Amounts follow token.decimals. ETH uses 18, while USDC and USDT use 6. Read the value from the token object rather than assuming 18.

Next steps