sodaVariants

What it is

sodaVariants are how SODAX makes assets usable across networks with liquidity attached.

When an asset exists natively on a network, SODAX uses the native asset directly. For example, SOL on Solana or BNB on BNB Chain. Some assets exist natively on several networks, such as USDC, USDT, or ETH, and SODAX will use the native version wherever it is available.

sodaVariants are introduced only on networks where an asset does not already exist natively. They extend that asset into new networks without replacing the native version elsewhere.

What it does inside SODAX

Inside the SODAX system, sodaVariants ensure that assets deployed on destination networks are immediately usable.

In many cross-network setups, an asset can be bridged or wrapped onto a network but still cannot be reliably traded or used because liquidity needs to be created locally. Applications are then forced to deploy and manage their own liquidity pools on every network they want to support, even when liquidity management is not their core product.

sodaVariants remove this problem. When a sodaVariant such as sodaETH or sodaBNB is made available on a network, it is directly connected to SODAX’s unified liquidity inventory. From day one, it can be traded, swapped, or used in execution flows without requiring applications to bootstrap local liquidity themselves.

Native assets continue to be used where they exist. sodaVariants are only used to extend assets into additional networks while keeping liquidity and execution coordinated at the system level.

Why it exists

Without sodaVariants, extending assets across networks creates a heavy burden for applications. Teams must manage both asset availability and deep liquidity across multiple chains, even when their real focus is building products, attracting users, or shipping features.

sodaVariants exist to remove this burden. They allow assets to be extended into new networks with liquidity already integrated into the SODAX system. This makes cross-network execution practical at scale without forcing every application to rebuild the same liquidity infrastructure over and over again.

What this means for users and partners

For users, assets behave the way they expect. They can trade or use assets across networks without worrying about whether liquidity exists on a specific chain.

For partners and builders, sodaVariants make cross-network support dramatically simpler. Assets are liquid by default and can even follow network-specific naming conventions (ETH.LL on LightLink Network or rETH on Redbelly Network). Because liquidity is handled at the system level, applications can choose to present these assets simply as “ETH” or “BNB” in their frontends.

The result is faster execution, fewer failed actions, and the ability to support multiple networks without fragmenting liquidity or product experience. This is what makes a true multi-network swap experience (often searched as multi chain swap) possible: assets are not just bridged, they arrive with depth already available for immediate use.