BNB Smart Chain (chainId 56) hosts the largest BEP-20 USDT footprint in EVM-land and remains a low-cost destination for stablecoin transfers among major EVMs. Reaching the chain takes one of three paths: a Binance withdrawal across BNB Chain rails, an onchain bridge that locks or burns the source token and mints the BEP-20 version, or a wallet-integrated aggregator. This guide walks through wallet setup, the ERC-20 to BEP-20 path for USDC and USDT, the trade-offs between centralized withdrawal and onchain bridging, and the failure modes that catch first-time users.
Adding BNB Chain (BSC) to your wallet
BNB Chain runs at chainId 56 with BNB as the native gas token. MetaMask, Rabby, Trust Wallet, and most EVM wallets ship the network pre-listed in 2026, after the Fermi hard fork in January dropped block time to 0.45 seconds and finality to roughly 1.125 seconds. Adding the network manually still works when needed: it is a five-line setup in any EVM wallet.
The Fermi hard fork changed the operating envelope for most bridges. To add BNB Chain manually in MetaMask, open the network selector and choose "Add a network":
Network name: BNB Smart Chain
RPC URL: https://bsc-dataseed.bnbchain.org
Chain ID: 56
Currency symbol: BNB
Block explorer: https://bscscan.com
The official RPC list lives at docs.bnbchain.org; Chainlist offers a one-click add. Public RPC throughput caps at 10K requests per 5 minutes.
The most common setup mistake is picking the wrong chainId. BNB Beacon Chain (legacy, chainId 714) and BNB Smart Chain (chainId 56) are different networks. Beacon Chain hosts BEP-2 assets; Smart Chain hosts BEP-20. Pick the one labeled "BNB Smart Chain" or "BSC."
ERC-20 to BEP-20: the canonical routes
The ERC-20 to BEP-20 path moves an Ethereum-native token to its BNB Chain representation. Three routes survive most use cases: a Binance withdrawal off-exchange, an onchain bridge that burns or locks the source token and mints the destination version, and a wallet-integrated aggregator that picks a bridge for you. Each preserves the dollar value but settles through different infrastructure.
The decision usually comes down to where the funds already sit. Funds on Binance reach BNB Chain via a network-selected withdrawal. Funds in self-custody on Ethereum reach BNB Chain via an onchain bridge. The three concrete routes:
Binance withdrawal: send the asset from Binance to a BNB Chain wallet address with "BEP-20 (BSC)" selected. Binance's withdrawal fee for USDT-BEP-20 is 0.1 USDT plus a small network fee. Settlement lands in roughly one block.
Onchain bridge: route through Stargate (LayerZero pools), Hyperlane (warp routes), Wormhole, Across, or a USDT0 mint-burn path. Fees and timing covered below.
Aggregator: open LI.FI, Jumper, Squid, or Rango. The aggregator quotes several bridges and routes through the cheapest or fastest. Eco Routes serves a similar function as an intent-based router across the rails above.
For funds already on a centralized venue, the venue's own BEP-20 rail minimizes moving parts. For a self-custody move, an established protocol with multi-year history and verifiable contracts on BscScan is the common choice.
Binance withdrawal vs onchain bridge tradeoffs
The Binance route settles off-chain on the exchange side and onchain only when the BEP-20 transaction is mined. An onchain bridge settles entirely onchain across both source and destination. The two mechanisms have different cost models and different operating envelopes.
A Binance BEP-20 USDT withdrawal carries a flat 0.1 USDT exchange fee plus a small BNB-denominated network fee, per Binance's fee page. It lands within roughly a minute. Availability depends on jurisdiction and account-level withdrawal limits.
An onchain bridge needs no exchange account. Costs decompose into source gas, destination gas, and a protocol or LP fee. Stargate's stablecoin pool LP fee sits between 0.01% and 0.06% per Stargate user docs. Hyperlane warp routes add a small relayer fee. Intent-based routes pay a solver spread instead.
Size matters. For sub-$1,000 transfers, the Binance route's flat fee usually wins on raw cost. For mid-five-figure transfers, a percentage-style bridge fee can beat the exchange spread plus withdrawal cost, especially when the asset is not already on the exchange.
Bridging USDC to BNB Chain
USDC on BNB Chain is a wrapped representation, not a Circle-issued native token. BNB Smart Chain is not a CCTP domain in 2026, so USDC arriving on BNB is bridged USDC, with a contract representing claims against USDC locked elsewhere. That changes the routing reality compared to chains where CCTP burn-mint is available.
Per Circle's supported chains list, CCTP V2 launched on Ethereum and Avalanche in March 2025 and rolled out through 2025 to Base, Arbitrum, Linea, OP Mainnet, Polygon, Unichain, World Chain, Sonic, and Codex. BNB Chain stayed off the list as of May 2026. Steps:
From Ethereum: open a bridge supporting USDC to BNB Chain. Stargate routes via its USDC pool; Wormhole offers a portal-wrapped variant; LI.FI and Jumper aggregate across both. Pick the source chain, set destination, paste address, approve.
From Binance: select USDC, choose "BEP-20" as the withdrawal network, paste the address, and confirm.
Confirm the receiving token matches what the destination dApp expects. Some BNB Chain protocols support only specific USDC variants. Check the contract on BscScan before swapping or supplying.
For native USDC functionality, bridge USDC to a CCTP-supported chain (Arbitrum, Base, Polygon), use that chain for USDC-native operations, and bridge only the necessary balance to BNB Chain when execution requires BNB-side liquidity.
Bridging USDT (BEP-20)
USDT on BNB Chain is the dominant stablecoin on the network by transfer volume. Two distinct token types exist: classic BEP-20 USDT, the Tether-issued canonical BNB Chain version, and USDT0, the LayerZero OFT version of USDT. They are not the same token. Holders of BEP-20 USDT cannot deposit it into a USDT0-only pool without first converting.
The canonical BEP-20 USDT contract is 0x55d398326f99059fF775485246999027B3197955. USDT0 is documented separately at eco.com.
Routes for sending USDT to BNB Chain:
From Binance: select USDT, set network to BEP-20, withdraw. 0.1 USDT exchange fee plus a small BNB network fee. Lands as canonical BEP-20 USDT.
From Ethereum, Solana, or another network: use Stargate's USDT pool or Hyperlane warp routes. Stargate lets users swap USDC on Ethereum for USDT on BNB in one route. Fees: source gas, 0.01% to 0.06% LP fee, destination gas.
USDT0 path: USDT0 burns on the source chain and mints on the destination via LayerZero. Per Chaos Labs, underlying USDT collateral stays locked in a vault while the omnichain wrapper moves. Settlement is one source plus one destination confirmation, zero slippage, no LP spread.
From Tron, bridge TRC-20 USDT through Allbridge or LayerZero to BEP-20, or send TRC-20 to a centralized venue and withdraw BEP-20. Route depth on Tron-EVM bridges varies week to week (see the USDT bridge networks guide).
What fees and timing should you expect on BNB Chain?
BNB Chain's post-Fermi 0.45-second block time and roughly 1.125-second finality mean the destination confirmation is rarely the bottleneck. The source chain dominates total time. An Ethereum-source bridge waits on Ethereum confirmations, typically 30 to 60 seconds for fast-finality protocols. The BNB-side mint or release lands almost immediately once the message arrives.
Fee rough ranges for BNB Chain bridging, May 2026:
Route | Total fee (USDT/USDC, $1,000 transfer) | Approximate time | Counterparty |
Binance withdrawal, BEP-20 | ~$0.50 (0.1 USDT + network) | 1 to 2 minutes | Binance custody |
Stargate, USDT or USDC pool | ~$1 to $3 (gas + 0.01%-0.06% LP) | 1 to 3 minutes | Stargate LP pools, LayerZero messaging |
USDT0 via LayerZero OFT | Source gas + messaging fee (~$0.50 to $2 on Ethereum) | 1 to 3 minutes | USDT0 vault, LayerZero DVN |
Hyperlane warp route | Source gas + relayer fee (~$1 to $2) | 1 to 5 minutes | Warp route deployer, Hyperlane validators |
Wormhole portal (wrapped USDC) | Source gas + ~$0.50 relayer fee | 2 to 5 minutes | Wormhole Guardians |
Aggregator (LI.FI, Jumper, Squid) | Routes through above plus ~0 to 0.1% spread | 1 to 5 minutes | Underlying bridge |
For fee mechanics across rails, see the bridge fees guide. For how these routes stack up for BNB Chain specifically, see the best BNB Chain bridge guide.
Common pitfalls
BNB Chain bridging failures cluster around a short list of recurring mistakes: wrong network on an exchange withdrawal, no BNB held for destination gas, mixed-up USDT variants, and Beacon-vs-Smart-Chain address confusion. Understanding these in advance saves recovery time and, in several cases, the funds themselves. The list below covers the failure modes that consistently surface in user support tickets.
The pitfalls:
Wrong network on a Binance withdrawal. USDT exists as ERC-20, BEP-20, TRC-20, Solana SPL, and others. Picking ERC-20 when the wallet expects BEP-20 sends funds to an Ethereum address with the same hex string. Recovery works only if the same private key controls the Ethereum address.
No BNB for gas on arrival. Every BNB Chain transaction needs BNB for gas. Bridge or withdraw a small amount (0.01 to 0.02 BNB is plenty) before or alongside the stablecoin transfer. Most aggregators offer a "gas top-up" toggle that delivers BNB with the bridged asset.
Confusing BEP-20 USDT and USDT0. Different contracts, routing, liquidity pools. A trade quoted against USDT0 will not fill against BEP-20 USDT. Check the contract on BscScan before any swap.
Wrapped USDC where native is expected. Stargate-wrapped USDC and Wormhole-portal USDC are different contracts; a Curve or PancakeSwap pool may only quote against one. Verify before bridging.
Beacon Chain vs Smart Chain. Sending BEP-20 to a Beacon Chain (BNB1 prefix) address fails. Sending BEP-2 to a Smart Chain (0x prefix) address also fails.
Stale liquidity in the bridge UI. Pool depth changes between quote and execution. For large transfers (over $50K stablecoin), refresh the quote before signing and consider splitting into smaller legs.
When a withdrawal lands on the wrong network, recovery depends on whether the same private key controls both addresses. For Ethereum-to-BSC mix-ups, the same address usually works on both chains; the wallet just switches networks to see the balance. For non-EVM mix-ups (Solana sent to a BEP-20 address), recovery is generally not possible without exchange support.
How does Eco Routes fit into BNB Chain bridging?
Eco Routes is an intent-based router that aggregates rails such as Hyperlane and LayerZero alongside the protocols listed above. The user expresses an intent like "deliver 1,000 USDC on BNB Chain," and a solver network competes to fill it at the best quoted rate. Settlement uses the same underlying bridges, with routing decided at the solver layer rather than the user layer.
Reference: Eco Routes overview.
Sources and methodology. Network parameters verified against BNB Chain docs and Chainlist on May 28, 2026. Binance fees pulled from the live Binance fee page. CCTP chain coverage verified against Circle developer docs. Fee ranges are approximate and refresh quarterly.