Canonical asset names (formerly sodaVariants)

Canonical asset names means every asset appears under its canonical parent name on every network where SODAX whitelists it: ETH is ETH, BTC is BTC, SOL is SOL. sodaVariants was an earlier SODAX term that described an older naming convention, and it is retired.

systemassetsliquiditycross-network

What it is

Canonical asset names is how SODAX presents assets across networks. An asset appears under its canonical parent name on every network where SODAX whitelists it: ETH is ETH, BTC is BTC, SOL is SOL, wherever a user meets it.

sodaVariants was an earlier SODAX term. It described an older naming convention for assets on networks where they are not native. The term is retired, and SODAX does not present assets under prefixed names.

What it does inside SODAX

An asset becomes usable on a network once SODAX whitelists it there. Asset whitelisting is the permissioned admission of an asset into the SODAX system once it meets liquidity, reliability and risk requirements. Whitelisting does not mean the system holds the asset in its liquidity inventory.

The Asset manager authorizes tokens and moves them into and out of the SODAX system. Whichever network a whitelisted asset is used on, apps calling the SODAX API see it under its canonical name, with liquidity attached for trading.

The same rule covers every asset category: crypto assets, stablecoins and tokenized assets (RWAs). SODAX whitelists tokenized assets like any other asset and never issues them.

Why it exists

Different names for the same asset on different networks leave users unsure what they actually hold. One canonical name per asset, on every network, keeps what a user sees consistent with what they asked for, and spares apps from renaming assets network by network.

What this means for users and partners

For users, an asset reads the same on every network where it is whitelisted.

For partners calling the SODAX API, every newly whitelisted asset lands in their app under its canonical name, with liquidity attached: no pools to bootstrap and no per-network renaming.

Related terms

Last updated: 11/11/2026