Avalanche: Networks & Assets

Avalanche is a spoke network in the SODAX System. User funds stay on Avalanche; the hub (Sonic) coordinates execution, and solvers settle against deep native liquidity on each network rather than isolated bridge pools. There are two asset lists to keep straight, and the difference is the point of SODAX:

Assets on Avalanche: the 7 assets that live on the C-Chain itself, AVAX and ERC-20 tokens. These are what your users hold, send, and receive on Avalanche; the entry and exit points of any Avalanche-side flow.
Assets across the SODAX System: 166 assets across all supported networks. Every one of them is a valid swap destination or collateral source for your Avalanche users, because every SODAX action is cross-network by default.

A user holding AVAX is not limited to the Avalanche-side list. They can swap AVAX into ETH on Ethereum, USDC on Base, SOL on Solana, or any other listed asset on any network, in one signed transaction. The on-Avalanche assets are simply where those journeys start and end on your side. Every count and list below is read live from the backend config API, GET https://api.sodax.com/v2/be/config/all, so it reflects what the backend serves today rather than what an SDK release has listed.

Assets on Avalanche

Live for swaps on Avalanche:

Live token list loads from the config API. If it has not appeared, read config.swaps.supportedTokens["0xa86a.avax"] from GET /v2/be/config/all, or use the SDK call below.

Live in the Money Market for supply, borrow, repay, and withdraw:

Live token list loads from the config API: config.moneyMarket.supportedTokens["0xa86a.avax"] in GET /v2/be/config/all.

Each address in these lists is a C-Chain contract address; AVAX uses the zero address. Look any of them up on the Avalanche Explorer. Hub vault addresses per asset are listed in Swaps: Compatible Assets.

Assets your users can reach

From an Avalanche-sourced action, users can trade, lend, and borrow across every SODAX-supported network:

Live network list loads from the config API: config.chains in GET /v2/be/config/all.

Chain identifiers come from ChainKeys.* in the SDK (ChainKeys.AVALANCHE_MAINNET = '0xa86a.avax'), and the live chain list from sodax.config.getSupportedSpokeChains(). Prefer the config call over hard-coding: networks are added over time.

Asset discovery in code

Never hard-code token addresses or asset lists; read them from the SDK config at runtime:

import { Sodax, ChainKeys } from '@sodax/sdk';

const sodax = new Sodax();

// Swappable assets on Avalanche
const swapTokens = sodax.swaps.getSupportedSwapTokensByChainId(ChainKeys.AVALANCHE_MAINNET);

// Money market assets on Avalanche
const mmTokens = sodax.moneyMarket.getSupportedTokensByChainId(ChainKeys.AVALANCHE_MAINNET);

These lists ship with the SDK package, so a token the backend has added since your SDK release appears in the live tables above before it appears here.

All deployment addresses by network: Mainnet Deployments
The full cross-network asset directory: sodax.com/partners/asset-directory

​Assets on Avalanche

​Assets your users can reach

​Asset discovery in code

Assets on Avalanche

Assets your users can reach

Asset discovery in code