Swaps on Arbitrum - SODAX Docs

SODAX swaps are intents, not bridges. Your user signs one transaction on Arbitrum that locks the input and declares what they want on the destination network. Solvers fill it; the SODAX relayer carries proof between Arbitrum, the hub (Sonic), and the destination. If nothing fills, the intent can be cancelled and funds recovered. From your side it is one SDK call. From your user’s side it is one wallet prompt, plus an approval the first time they swap an ERC-20.

What this looks like on Arbitrum

Source: the intent transaction is an ordinary EVM transaction on Arbitrum One, signed by the user’s wallet. ChainKeys.ARBITRUM_MAINNET ('0xa4b1.arbitrum') identifies the network everywhere in the SDK.
Reach: any solver-compatible asset on any SODAX network is a valid destination, 166 assets today. The on-Arbitrum asset list only bounds what users hold on Arbitrum itself, not what they can swap into.
Tokens: ETH plus standard ERC-20s. Read addresses and decimals from the SDK config; never hard-code them.
Settlement: output lands on the destination network at dstAddress. Swaps into Arbitrum settle as ordinary ETH or ERC-20 balances at the recipient address.

Approvals

swap() does not approve the input token for you. ETH is the native token and needs no approval. Every ERC-20 does: SODAX’s asset manager pulls it through the ERC-20 interface, so check the allowance first and approve when it falls short.

const allowance = await sodax.swaps.isAllowanceValid({ params, walletProvider });
if (!allowance.ok) throw allowance.error;

if (!allowance.value) {
  const approval = await sodax.swaps.approve({ params, walletProvider });
  if (!approval.ok) throw approval.error;
  // wait for the approval to be mined before calling swap()
}

params is the same intent params object you pass to swap().

Quoting

The solver API quotes both directions:

const quoteResult = await sodax.swaps.getQuote({
  token_src: eth.address,             // token on Arbitrum
  token_dst: usdc.address,            // token on the destination network
  token_src_blockchain_id: ChainKeys.ARBITRUM_MAINNET,
  token_dst_blockchain_id: ChainKeys.ETHEREUM_MAINNET,
  amount: 10n ** BigInt(eth.decimals) / 10n, // 0.1 ETH
  quote_type: 'exact_input',          // the only supported quote type
});

getQuote deducts any configured partner fee before quoting, so quoted_amount is the net output the user actually receives.

Fees

Using SODAX is free to integrate. Two fees can apply to a trade:

Base fee: a fixed 0.1% of the input, taken by the protocol. Not configurable; compute it ahead of time with getSolverFee(inputAmount).
Your fee: optional platform fee on top, set by you and paid to you. It is the only fee you control. Configure it at SDK setup and check it with getPartnerFee(inputAmount). See Monetize SDK.

The user also pays Arbitrum’s network fee for the intent transaction, in ETH. Arbitrum folds the cost of posting the transaction to Ethereum into its gas estimate, so the gas units from sodax.swaps.estimateGas times the current gas price cover the whole fee. See How to estimate gas in Arbitrum and Estimate Gas.

Executing

Prefer swap(). It creates the intent on Arbitrum, verifies it landed, submits it to the relay, waits for the packet on the hub, and notifies the solver. The Quickstart has the complete call. Track progress with getStatus(request), and cancel unfilled intents with cancelIntent. Limit orders (intents without deadlines) work from Arbitrum too, via createLimitOrder. Orchestrating manually with createIntent and submitIntent works the same as on any EVM network: Arbitrum intents need no relay extra data.

Error handling

Operations return Result<T> instead of throwing. The core methods (swap, createIntent, postExecution) return a typed SodaxError union you can switch on by error.code.

Full reference, including raw mode, limit orders, cancellation, and the complete error-code table: Swaps.

​What this looks like on Arbitrum

​Approvals

​Quoting

​Fees

​Executing

​Error handling