Quick summary — who this guide is for
This guide explains how to move tokens between chains using Trust Wallet as your interface: from preparation to execution, what can go wrong, and how to recover stuck funds. If you want practical steps for how to swap bep20 to erc20 trust wallet, or to bridge tokens trust wallet across chains, you’ll find step-by-step procedures and safety tips here.
Who this guide is for
- Mobile-first DeFi users who run a non-custodial (hot) software wallet.
- People who need to move tokens between EVM-compatible chains (BEP20 ↔ ERC20) or use bridge dApps.
Who should look elsewhere
- Users who prefer custody (custodial exchange transfers can be simpler).
- Anyone who needs institutional-level guarantees — a hot wallet adds convenience but not the same security as a hardware setup.
If you need help with installing Trust Wallet first, see the mobile setup pages: Install on iPhone and Install on Android.
Basics: what is bridging and token standards
A cross-chain bridge moves value between different blockchains by locking an asset on one chain and minting a representation on another (or by redeeming a wrapped token). BEP20 and ERC20 are token standards on Binance Smart Chain (BSC) and Ethereum respectively; they define how tokens behave on each chain. Why does this matter? Because a token's contract address and standard determine whether your wallet will show the balance automatically or if you must add a custom token after bridging.
For background on token mechanics and supported chains, see token-standards-and-bridges and multi-chain support.
How Trust Wallet fits into cross-chain transfers
Trust Wallet is a hot software wallet that holds your private keys locally and can act as the signer when you use bridge dApps. But one subtle point: an in-wallet swap typically stays on the same chain. Cross-chain transfers usually require a bridge dApp (accessed via the in-app dApp browser where available) or WalletConnect to connect your mobile wallet to external bridge sites.
In my experience, on Android the in-app dApp browser streamlines the flow. On iPhone I often use WalletConnect to link Trust Wallet to a bridge page in Safari (Apple's rules limit some in-app browsers). What I've found makes a real difference is doing a tiny test bridge first (more on that below).
Methods compared: in-app swap vs bridge dApp vs custodial transfer
| Method |
How it works |
Pros |
Cons |
| In-app swap (same chain) |
On-chain swap between tokens on same blockchain |
Fast, low friction |
Can't change token standard (no cross-chain) |
| Bridge dApp (via in-app browser / WalletConnect) |
Lock & mint or burn & release across chains |
Non-custodial, broad chain support |
Longer wait times, more risk if bridge contract is malicious |
| Custodial transfer (exchange) |
Send token to exchange, withdraw on other chain |
Familiar UX, support available |
Custodial custody, KYC, withdrawal limits |
(Image: bridge-flow-diagram.png — alt: Placeholder flow diagram showing lock-and-mint bridge steps)
Step-by-step: how to swap BEP20 to ERC20 Trust Wallet
This is a generic sequence for bridging tokens trust wallet to another chain. Exact screens depend on the bridge dApp you choose.
- Prepare your wallet: make sure you have BNB (for BSC gas) and ETH (for Ethereum gas) available in the respective accounts. (Yes — two wallets.)
- Add the token on the source chain to your wallet so you can approve it. See add-custom-token if it doesn't appear.
- Open the bridge dApp. On Android use the DApp browser. On iPhone use WalletConnect via the walletconnect guide or open the bridge in Safari and connect.
- Select source chain = BSC (BEP20), destination = Ethereum (ERC20), and the token to bridge.
- Approve the token allowance (this is on-chain approval). Keep approvals minimal and avoid setting unlimited allowance when possible.
- Execute the bridge transaction and confirm in Trust Wallet. You may see multiple transactions — an approval and the bridge transfer.
- Wait for finality. Bridges can take minutes to hours depending on confirmations and relayer batching.
- Add the destination token contract to your wallet if the balance doesn’t show automatically. Use the token contract provided by the bridge (verify carefully).
For a quick reference on gas fee behavior and how EIP-1559 affects priority fees, read gas-fees-and-optimization.
After the bridge: verifying tokens and common follow-ups
- Check the transaction hash on both chain explorers. Did the bridge report a destination tx? If yes, copy that hash.
- Add the token manually if you don't see it. (Token addresses differ across standards.)
- If you bridged wrapped tokens, you may need to unwrap them on the destination chain.
If you want to remove a token approval after the bridge, use the guide: revoke token approvals.
Troubleshooting: unstuck bridged tokens and recovery steps
What if the token never appears? First, don't panic. Follow these steps in order:
- Confirm the source TX is confirmed on the source chain explorer.
- Check the bridge transaction log — many bridges provide a status page with the destination TX hash.
- If the bridge reports success but wallet shows nothing, add the destination token contract manually using the correct chain network (see add-custom-token).
- If the bridge failed or timed out, check whether the bridge has a recover or refund process (read its docs; many provide a support ticket flow).
- Contact bridge support only after collecting TX hashes and screenshots. And never share your seed phrase or private keys.
If you still get stuck, my go-to is to gather evidence (TX hashes on both chains) and then follow the troubleshooting checklist at troubleshooting.
Bridge security considerations and best practices
Bridges are attractive targets. Here are things to watch for:
- Contract audits and reputation matter, but audits are not guarantees. Ask: who runs the bridge and how does it custody or collateralize assets?
- Phishing dApps can mimic bridge UIs. Verify the URL and, if possible, use WalletConnect to reduce copy-paste risk.
- Approvals: never approve unlimited allowances for unknown contracts. I once almost approved a malicious contract; stopping the approval saved me from a bad outcome.
- Test with a small amount first. Seriously — a $5 test is cheap insurance.
- Consider hardware wallet confirmation for high-value moves (Trust Wallet can export private keys if you use a hardware solution; see export-private-key for options).
For a deeper checklist, see security-features and transaction-simulation-safety.
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets trade some security for convenience. They work well for active DeFi use, but for large, long-term holdings a hardware wallet reduces risk. See security-best-practices and ledger-hardware.
Q: How do I revoke token approvals?
A: Use the revoke guide: revoke-approvals-and-allowances. Revoke the approval contract on the chain you used to bridge.
Q: What happens if I lose my phone?
A: If you have a seed phrase backup you can restore your wallet on another device. For detailed steps, see lost-phone-recovery. Never store the seed phrase in cloud notes without encryption.
Conclusion & next steps
Bridging is powerful but adds attack surface and complexity compared with same-chain swaps. My practical advice: always do a small test transfer, check contract addresses twice, and keep transaction hashes handy in case you need help. If you want more step-by-step coverage of related features, read the in-wallet swap overview and the cross-chain bridges page.
If you're ready to bridge, start with a small test amount and follow the checks above. And if you run into trouble, the troubleshooting links in this guide are where to start.
