Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on Arbitrum. The Arbitrum side is contract-tracked rather than a native gas balance. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
Arbitrum inclusion and its ethereum settlement are distinct from final receipt on Ethereum. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
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.
BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Arbitrum. EVM 0x account address On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
Arbitrum 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. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Route-specific mistakes include sending on a network other than Arbitrum; using a destination that is not valid for Ethereum; running out of ETH before the source transaction is submitted. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this ARB on Arbitrum to BNB 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.
ARB is a contract representation on Arbitrum at 0x912ce59144191c1204e64559fe8253a0e49e6548. ETH, not ARB, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
BNB is a contract representation on Ethereum at 0xb8c77482e45f1f44de1745f52c74426c631bdd52. ETH, not BNB, 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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On receipt, Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
ARB is the deposited token input; BNB is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
ETH is the native gas asset for Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. ARB is token-tracked and can need approval before transfer.
Sending ARB on a network other than Arbitrum, 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.
Requirements are checked for the live ARB Arbitrum to BNB 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.
