Bitcoin, Sui, Stellar and other non-EVM routes

Most routing infrastructure assumes Ethereum-style accounts: a 20-byte address, ERC-20 approvals, a nonce. Solana, Sui, Stellar, NEAR and Bitcoin each break at least one of those assumptions, so supporting them is a separate integration per chain rather than one more chain ID. That is why a pair like SUI to SOL is awkward almost everywhere.

SODAX handles this by treating each non-EVM chain as a spoke with its own contracts, connected to a hub chain (Sonic) where intents are matched. An intent from Sui to Solana is created on Sui, relayed to the hub, and filled by a solver on Solana. You sign once, on the source chain, in that chain's native wallet.

Destination addresses differ by chain: base58 on Solana, 0x-prefixed 64 hex characters on Sui, G-prefixed on Stellar, bc1 or 1 or 3 on Bitcoin. Sending to the wrong format is caught by validation; sending to a valid address on the wrong network is not, and is unrecoverable. Paste, then read it back.

Bitcoin dominates: around 20 minutes to a safe confirmation, so a BTC route is slow regardless of what happens downstream. Sui, Solana, Stellar and NEAR finalise in under a minute. The estimate shown per route is the sum of source finality, relay and destination.

Wallet execution is available for EVM networks and Solana. Bitcoin, Sui, Stellar, NEAR, Injective, Stacks, Hedera and ICON routes are quoted with live numbers, and the app says before you connect that execution for those wallets is not yet built in. The quote is still useful: it is the same API a provider's own app uses.