Sei Wallets and the Polygon to Base Route
How Sei balances relate to the Polygon to Base route.
Why this matters on Sei
Polygon-to-Base is a cross-chain move, even though both ecosystems support many familiar assets. Confirm the exact destination representation before using the received balance.
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 Polygon 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 Polygon for this route to apply.
Leaving Polygon
Compare Polygon transaction costs with bridge and liquidity costs when consolidating small balances. Check network selection and contract addresses before signing, especially when an asset also exists on Ethereum.
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
- 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.
- Send a small test amount first if the route or address is new to you.
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