Sei Wallets and the Arbitrum to Base Route
How Sei balances relate to the Arbitrum to Base route.
Why this matters on Sei
Moving between Arbitrum and Base can be straightforward when a supported route exists, but route availability and costs can change. Check the live quote immediately before execution.
Sei has its own network environment and may expose different application and asset conventions depending on the wallet and ecosystem.
Sei can expose different asset and application conventions depending on the wallet and ecosystem you use, so confirm which environment a balance belongs to before acting on it.
Sei and this route
Sei is neither end of the Arbitrum to Base route, but a wallet that uses Sei often holds balances on those networks too. If your assets are on Sei, they would first have to be on Arbitrum for this route to apply.
Leaving Arbitrum
Compare L2 transaction costs with any bridge or liquidity costs required to reach the destination. Verify the network, contract and destination before signing cross-chain transactions.
Arriving on Base
Verify the token contract on Base and do not rely on ticker or logo alone. Consider Base transaction costs together with bridge and route costs when moving small balances.
Sei: what to pay attention to
- Costs: Compare the complete network and route costs before moving small balances.
- Security: Confirm network, destination and transaction details before signing.
- Assets and tokens: Verify the network-specific asset representation.
A Sei checklist for this topic
- Do not assume a route from Sei is available; check the current interface and quote.
- Send a small test amount first if the route or address is new to you.
- Confirm that the token you hold on Sei is supported for the route you are reading about.
- Verify the source network, the destination network and the destination address before signing.
Bridge from Sei
Compare the complete network and route costs before moving small balances. On the Sui side: verify the network-specific asset and object details rather than applying EVM assumptions.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Sei → Sui BRIDGE GUIDE