Skip to main content
HyperEVM is a spoke network in the SODAX System. User funds stay on HyperEVM; 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 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.
A user holding HYPE is not limited to the HyperEVM-side list. They can swap HYPE into ETH on Ethereum, USDC on Base, SOL on Solana, or any other listed asset on any network, in one signed transaction. The on-HyperEVM 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 HyperEVM

Live for swaps on HyperEVM:
Live token list loads from the config API. If it has not appeared, read config.swaps.supportedTokens.hyper 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.hyper in GET /v2/be/config/all.
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.

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: config.chains in GET /v2/be/config/all.
Chain identifiers come from 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:
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.