- Assets on HyperEVM: the 10 assets that live on HyperEVM itself, HYPE and ERC-20 tokens. These are what your users hold, send, and receive on HyperEVM; the entry and exit points of any HyperEVM-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 HyperEVM users, because every SODAX action is cross-network by default.
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 HyperEVM
Live for swaps on HyperEVM:Live token list loads from the config API. If it has not appeared, read
Live in the Money Market for supply, borrow, repay, and withdraw:
config.swaps.supportedTokens.hyper from GET /v2/be/config/all, or use the SDK call below.Live token list loads from the config API:
Each address in these lists is a HyperEVM contract address; HYPE uses the zero address. These are HyperEVM tokens only: a balance in HyperCore spot becomes usable once the user transfers it to HyperEVM, and only if the HyperEVM token is in the list. Look any address up on HyperEVMScan.
Hub vault addresses per asset are listed in Swaps: Compatible Assets.
config.moneyMarket.supportedTokens.hyper in GET /v2/be/config/all.Assets your users can reach
From a HyperEVM-sourced action, users can trade, lend, and borrow across every SODAX-supported network:Live network list loads from the config API:
Chain identifiers come from config.chains in GET /v2/be/config/all.ChainKeys.* in the SDK (ChainKeys.HYPEREVM_MAINNET = 'hyper'), 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:- All deployment addresses by network: Mainnet Deployments
- The full cross-network asset directory: sodax.com/partners/asset-directory