lifi bridge is a cross-chain aggregator that finds bridge and decentralized exchange routes between major EVM networks, including Ethereum, Arbitrum and Base, and non-EVM networks such as Solana. For a planned transfer, lifi bridge helps you find out whether your source chain, destination chain and tokens have a route. Coverage follows its integrated bridges and exchanges, so the live chain list can change as integrations are added.
Which Chains Does lifi bridge Support?
The LI.FI cross-chain bridge supports Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain and Avalanche, alongside non-EVM chains such as Solana. Ethereum, BNB Chain and Avalanche are EVM-compatible Layer 1 networks; Arbitrum, Optimism and Base are Ethereum Layer 2 networks. Solana uses a different execution system, but it is part of LI.FI’s chain coverage.
Crossing between those networks depends on an integrated bridge. Solana routes can use bridges such as Mayan and Circle CCTP; CCTP carries USDC between supported chains. Decentralized exchanges can swap tokens before or after the bridge step, giving the router more possible paths than a direct transfer of one asset.
How Do You Check the Current Chain List?
The lifi bridge API exposes GET /v1/chains for a current list of supported networks. To include EVM and non-EVM chains, set chainTypes=EVM,SVM,UTXO,MVM,TVM,STL; the default request returns EVM chains. The LI.FI API reference documents that filter and the chain data returned. For a quick manual check, use the LI.FI Widget’s chain selector.
The list changes when LI.FI adds integrations that reach more chains. A new bridge connection can make another network reachable; a new exchange integration can add swap choices on a network already covered. That is why the live response is more useful than an older chain count when you are planning a transfer.
Why Can a Listed Chain Return No Route?
A listed chain can return no route when the available bridges and swaps cannot connect your particular source token to your destination token. Three parts determine the result:
-
Chains: Where the transfer starts and ends.
-
Tokens: The exact assets on those chains, including whether a token is a native or bridged version.
-
Route: An available sequence of swaps and bridge steps for that pair.
Those parts have to connect for the quoted amount. Say you hold a less common token on Base and want a token on Solana. Both chains may be listed, yet the router still needs a bridge that carries an eligible asset and, where necessary, exchanges with liquidity for the swaps on either side. The GET /v1/tokens endpoint helps identify the available token versions on each chain; a route request then tests the specific pair.
Try USDC or the chain’s native token, such as ETH or SOL, and request a fresh route. If that pair still has no route, try another destination chain. The new request tells you which transfer is available now.