Sei Wallets and the Base to Arbitrum Route

Why this matters on Sei

Base and Arbitrum are both L2 environments, but that does not make their token contracts interchangeable. Treat the destination token as a network-specific asset.

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 Base to Arbitrum 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 Base for this route to apply.

Leaving Base

Consider Base transaction costs together with bridge and route costs when moving small balances. Use trusted interfaces and verify destination network and token before signing.

Arriving on Arbitrum

Confirm the Arbitrum token contract rather than assuming an identical ticker represents the same asset everywhere. Compare L2 transaction costs with any bridge or liquidity costs required to reach the destination.

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

• Verify the source network, the destination network and the destination address before signing.
• Compare quotes and the minimum received amount, since the final amount can differ from the estimate.
• Keep enough native balance on the source network to pay for the transaction.
• Do not assume a route from Sei is available; check the current interface and quote.

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.

Related guides