Hedera: Networks & Assets

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

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

Live for swaps on Hedera:

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

Each address in these lists is the EVM form of a Hedera token ID: the token ID’s number, zero-padded to 20 bytes. USDC, token 0.0.456858, is 0x000000000000000000000000000000000006f89a. HBAR uses the zero address. To look a token up on HashScan or the mirror node, convert the address back to its token ID: 0.0.${BigInt(address)}. Hub vault addresses per asset are listed in Swaps: Compatible Assets.

Assets your users can reach

From a Hedera-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.HEDERA_MAINNET = 'hedera'), 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 Hedera
const swapTokens = sodax.swaps.getSupportedSwapTokensByChainId(ChainKeys.HEDERA_MAINNET);

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

​Assets your users can reach

​Asset discovery in code

Assets on Hedera

Assets your users can reach

Asset discovery in code