Bridge USDC from Scroll to BNB Chain

FromScroll
ToBNB Chain
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

Direction

Scroll → BNB Chain

Asset

USDC

Source gas

ETH

Destination gas

BNB

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Scroll network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and BNB Chain destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

USDC representation on both sides

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset. The same stablecoin ticker does not make the two network records or contracts interchangeable.

ETH source gas and BNB destination readiness

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

Leaving Scroll L2 for BNB Chain L1

Scroll inclusion and its ethereum settlement are distinct from final receipt on BNB Chain. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.

Scroll deposit-side execution

Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Scroll. EVM 0x account address A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently.

BNB Chain receipt-side execution

BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays destination-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

Scroll to BNB Chain bridge mistakes

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for BNB Chain; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Private Route for USDC → USDC

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Scroll to USDC on BNB Chain path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.

  • Reduces the obvious link between the USDC deposit and USDC receipt
  • Compare standard and Private Route options for Scroll → BNB Chain
  • Shows what remains public on Scroll and BNB Chain before you deposit
Check Private Route availability →

Related routes

Scroll to BNB Chain FAQs

What USDC representation leaves Scroll?

USDC is a contract representation on Scroll with 6 decimals at 0x06eFdBFf2a14a7c8E15944D1F4A48F9F95F663A4. ETH, not USDC, pays gas unless both symbols are the same. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset.

What USDC representation arrives on BNB Chain?

USDC is a contract representation on BNB Chain with 18 decimals at 0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d. BNB, not USDC, pays gas unless both symbols are the same. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.

Does the same USDC ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a USDC contract token and a USDC contract token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a Scroll address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Scroll, selecting a representation not listed by the quote, or entering an address invalid for BNB Chain can prevent normal detection or receipt.

Can I bridge USDC from Scroll to BNB Chain without KYC?

Requirements are checked for the live USDC Scroll to BNB Chain quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.

View all bridge FAQs →