How to switch between networks like Ethereum and BSC in Exodus?

Network Selection Interface

1. Open the Exodus desktop or mobile application and unlock your wallet using your password or biometric authentication.

2. Navigate to the asset dashboard where your cryptocurrency balances are displayed.

3. Tap or click on the specific token you wish to interact with—such as ETH or BNB—to access its asset details page.

4. Look for a gear icon or “Network” label adjacent to the token name or balance; this opens the network configuration panel.

5. A dropdown menu appears listing all supported networks for that asset, including Ethereum Mainnet, BSC, Polygon, and Arbitrum.

Asset-Specific Network Rules

1. Not every token supports cross-chain functionality within Exodus—only assets deployed natively on multiple chains appear with switchable network options.

2. ETH exists only on Ethereum Mainnet by design; attempting to send it to BSC requires wrapping via a bridge, which Exodus does not facilitate directly from the network selector.

3. BUSD and USDT have versions on both Ethereum and BSC; Exodus displays them separately under their respective network labels to avoid confusion.

4. When switching networks for a multi-chain token, the balance shown updates instantly to reflect holdings on the selected chain—if no balance exists there, it displays zero.

5. Transaction history remains segmented per network—transfers on BSC do not merge with Ethereum transaction logs in the UI.

Transaction Initiation and Confirmation

1. After selecting BSC for a compatible token, the “Send” button activates the BSC-compatible transaction flow, including gas fee estimation in BNB.

2. The recipient address field validates format compliance—BSC addresses match Ethereum’s 0x format but will fail if sent to an incompatible contract on Ethereum.

3. Gas settings appear as sliders labeled “Slow”, “Average”, and “Fast”, corresponding to BSC’s real-time network congestion levels.

4. Before final confirmation, Exodus displays a warning banner if the selected network differs from the recipient’s expected chain—this prevents accidental cross-chain sends without bridging.

5. Once confirmed, the transaction hash is generated on BSC’s blockchain and appears under the “Activity” tab with a BSC block explorer link.

Wallet Address Consistency Across Chains

1. Your Exodus wallet address remains identical across Ethereum and BSC because both use the same ECDSA key derivation standard.

2. This means one private key controls ETH on Ethereum and BNB on BSC—but assets are isolated by chain and require separate balance tracking.

3. Deposits made to your address on BSC automatically appear in Exodus only after the network confirms the transaction and the wallet syncs the BSC node data.

4. Exodus does not auto-import tokens from external chains—you must manually add custom tokens using contract addresses and decimals if they aren’t preloaded.

5. Switching networks does not alter your seed phrase, private keys, or recovery method—it only changes the active blockchain context for viewing and transacting.

Frequently Asked Questions

Q: Can I hold ETH and BNB in the same Exodus wallet?A: Yes. ETH resides on Ethereum Mainnet and BNB on BSC; both coexist under one wallet interface with distinct balance entries.

Q: Why does my USDC balance show zero on BSC even though I hold it on Ethereum?A: USDC on Ethereum and USDC on BSC are separate tokens with different contracts—Exodus treats them as distinct assets unless manually added on BSC.

Q: Does Exodus support sending tokens from Ethereum to BSC directly?A: No. Exodus does not integrate bridges. You must use an external service like Multichain or Binance Bridge before importing BSC-based tokens into Exodus.

Q: What happens if I select the wrong network before sending?A: The transaction will execute on the selected chain. If the recipient address has no balance or contract on that chain, funds may become irretrievable without prior bridging setup.