Skip to main content

​
Do I need to write or deploy a contract?

No. SODAX’s LightLink 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. Your user signs one EVM transaction on LightLink 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. Swaps into LightLink settle as ordinary ETH or ERC-20 balances at the recipient’s LightLink address. If an intent is never filled, it can be cancelled and the funds recovered. Two answers, and the difference matters. On LightLink itself, 14 assets are live for swaps: ETH plus LightLink ERC-20 tokens, including bnUSD, SODA, USDC, LL, and .LL versions of assets from other networks. 16 assets work in the money market, and that list includes tokens the swap list does not. But your users are not limited to the LightLink-side lists. Every swap is cross-network, so from LightLink they can reach all 166 assets across every SODAX-supported network. Both lists grow as the backend config adds them; read them from sodax.config at runtime, or see the live tables in Networks & Assets. No. LightLink’s Enterprise Mode makes transactions gasless for contracts a project registers and pays for, but the SDK sends SODAX transactions on LightLink as standard EVM transactions. Users pay gas in ETH, so the signing account needs ETH on LightLink, even when it is swapping or supplying another token.

​
Is LL the gas token?

No. ETH is LightLink’s native gas token. LL is an ERC-20 token on LightLink, swapped and approved like any other ERC-20.

​
Why is my BTC.LL amount off by 10^10?

Because .LL tokens use 18 decimals, while BTC uses 8 on Bitcoin. An amount built with 8 decimals is 10^10 too small on LightLink. Build every amount from token.decimals of the LightLink token itself.

​
Is there an approve step before swapping or supplying?

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

​
Which RPC endpoint should I use?

Any LightLink Phoenix mainnet RPC. The SODAX config uses LightLink’s replicator, https://replicator.phoenix.lightlink.io/rpc/v1; pass your own 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, LightLink 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 LightLink network fees in ETH. 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.