Swap BNB on Polygon to ARB on Ethereum

FromPolygon
ToEthereum
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.
ARB / USD
Price
24h
High
Low
Vol

What you need to know

BNB input identity and handling

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Polygon. The recorded Polygon 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.

Ethereum destination execution

Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Ethereum. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.

ARB output identity and receiving

Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.

Polygon source execution

Polygon is a L1 EVM network in the Polygon ecosystem. POL pays source-side network gas on Polygon. EVM 0x account address A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.

EVM-to-EVM execution boundary

Polygon and Ethereum can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.

Mistakes specific to BNB Polygon to ARB Ethereum

Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Ethereum; running out of POL before the source transaction is submitted. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.

Private Route for BNB → ARB

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

Related routes

Swap BNB on Polygon to ARB on Ethereum FAQs

What exactly leaves Polygon as BNB?

BNB is a contract representation on Polygon with 18 decimals at 0x5c4b7CCBF908E64F32e12c6650ec0C96d717f03F. POL, not BNB, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.

What exactly arrives on Ethereum as ARB?

ARB is a contract representation on Ethereum at 0xb50721bcf8d664c30412cfbc6cf7a15145234ad1. ETH, not ARB, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.

Why does the BNB to ARB direction matter?

Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.

What changes between the source and destination asset roles?

BNB is the deposited native-asset input; ARB is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending BNB?

Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.

What funds the Polygon source transaction?

POL is the native gas asset for Polygon. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. BNB is token-tracked and can need approval before transfer.

What is the most dangerous wrong-network mistake here?

Sending BNB on a network other than Polygon, or using an address that is not valid for Ethereum, can prevent detection or delivery. Match both network labels and representations to the active route.

Can I swap BNB on Polygon to ARB on Ethereum without KYC?

Requirements are checked for the live BNB Polygon to ARB Ethereum 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 Help Center FAQs →