Bridge USDC from Solana to BNB Chain

FromSolana
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

Solana → BNB Chain

Asset

USDC

Source gas

SOL

Destination gas

BNB

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Solana 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

Move from a Solana account into BNB Chain EVM

Solana uses Solana accounts and SOL for source fees, while BNB Chain uses an EVM 0x account and BNB for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. USDC is read from its Solana mint or native account, while USDC arrives at the quoted BNB Chain native or contract representation.

USDC mint and SOL fee checks

Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 mint/account selected by the quote must match the source wallet balance.

BNB Chain contract and 0x receiving checks

EVM 0x account address BNB is the native gas asset for BNB Chain. 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. A Solana address cannot receive this EVM-side output.

USDC keeps its ticker while changing ledgers

USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. Native USDC exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make USDC contracts interchangeable across networks. USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. The BNB Chain side is contract-tracked rather than a native gas balance. Native USDC exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make USDC contracts interchangeable across networks. USDC leaves as a network-specific contract asset. USDC arrives as a network-specific contract asset.

Solana to BNB Chain bridge mistakes

Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for BNB Chain; running out of SOL before the source transaction is submitted; assuming solana and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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

Solana account, token, program, signature, and fee activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Solana to USDC on BNB Chain path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana 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 Solana → BNB Chain
  • Shows what remains public on Solana and BNB Chain before you deposit
Check Private Route availability →

Related routes

Solana to BNB Chain FAQs

What changes between the Solana source and BNB Chain receipt?

The source uses a Solana signature, mint or native account, and SOL fees. The destination uses a 0x account, BNB gas, and the quoted EVM token contract or native balance.

What USDC representation leaves Solana?

USDC is a contract representation on Solana at EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v. SOL, not USDC, pays gas unless both symbols are the same. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 Solana address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Solana, 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 Solana to BNB Chain without KYC?

Requirements are checked for the live USDC Solana 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 →