BNB Chain: Networks & Assets

BNB Chain is a spoke network in the SODAX System. User funds stay on BNB Chain; 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 BNB Chain: the 18 assets that live on BNB Chain itself, BNB and BEP-20 tokens. These are what your users hold, send, and receive on BNB Chain; the entry and exit points of any BNB Chain-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 BNB Chain users, because every SODAX action is cross-network by default.

A user holding BNB is not limited to the BNB Chain-side list. They can swap it into ETH on Ethereum, USDC on Base, SOL on Solana, or any other listed asset on any network, in one signed transaction. The on-BNB Chain 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 BNB Chain

Live for swaps on BNB Chain:

Live token list loads from the config API. If it has not appeared, read config.swaps.supportedTokens["0x38.bsc"] 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["0x38.bsc"] in GET /v2/be/config/all.

The two lists overlap but differ: some tokens are swap-only and some are money-market-only, so check the list for the action you are building. Addresses are BEP-20 contract addresses on BNB Smart Chain; BNB uses the zero address. Two things to check when you read this list:

Decimals. USDC and USDT use 18 decimals on BNB Chain, as do most other tokens here. Read decimals per token; do not assume the value a token has on another network.
Symbols. SODAX symbols are not always the token’s on-chain symbol. Binance-Peg ETH reports ETH on-chain and is ETHB in the SODAX list. Where it matters, match by address.

Hub vault addresses per asset are listed in Swaps: Compatible Assets.

Assets your users can reach

From a BNB Chain-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.BSC_MAINNET = '0x38.bsc'), 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 BNB Chain
const swapTokens = sodax.swaps.getSupportedSwapTokensByChainId(ChainKeys.BSC_MAINNET);

// Money market assets on BNB Chain
const mmTokens = sodax.moneyMarket.getSupportedTokensByChainId(ChainKeys.BSC_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 BNB Chain

​Assets your users can reach

​Asset discovery in code

Assets on BNB Chain

Assets your users can reach

Asset discovery in code