Bridge BNB from Linea to Arbitrum

FromLinea
ToArbitrum
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

Linea → Arbitrum

Asset

BNB

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the BNB asset and Linea network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Arbitrum 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

BNB source representation

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Linea. The recorded Linea representation uses 18 decimal places. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.

Linea to Arbitrum L2 handoff

This route crosses two L2 execution environments. Linea settles to ethereum, while Arbitrum settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.

BNB destination representation

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Arbitrum receipt-side execution

Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Arbitrum. EVM 0x account address An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately.

Linea deposit-side execution

Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Linea. EVM 0x account address A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones.

Linea to Arbitrum bridge mistakes

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for Arbitrum; running out of ETH before the source transaction is submitted. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Private Route for BNB → BNB

Linea wallet, token-transfer, contract, log, and gas activity remain public, and Arbitrum wallet, token-transfer, contract, log, and gas activity remain public. For this BNB on Linea to BNB on Arbitrum 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 BNB deposit and BNB receipt
  • Compare standard and Private Route options for Linea → Arbitrum
  • Shows what remains public on Linea and Arbitrum before you deposit
Check Private Route availability →

Related routes

Linea to Arbitrum FAQs

What BNB representation leaves Linea?

BNB is a contract representation on Linea with 18 decimals at 0xf5C6825015280CdfD0b56903F9F8B5A2233476F5. ETH, not BNB, pays gas unless both symbols are the same. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.

What BNB representation arrives on Arbitrum?

BNB is a contract representation on Arbitrum with 18 decimals at 0x20865e63B111B2649ef829EC220536c82C58ad7B. ETH, not BNB, pays gas unless both symbols are the same. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Does the same BNB ticker guarantee the same ledger form?

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

Which gas balances matter for this bridge?

A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. 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 Linea address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge BNB from Linea to Arbitrum without KYC?

Requirements are checked for the live BNB Linea to Arbitrum 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 →