Swap WETH on Scroll to XRP on 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.
XRP / USD
Price
24h
High
Low
Vol

What you need to know

WETH input identity and handling

WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Scroll. The recorded Scroll representation uses 18 decimal places. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.

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.

WETH unwrap or exchange input check

WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. On this route WETH is the source token on Scroll. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

BNB Chain destination 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.

XRP output identity and receiving

XRP is classified as a native asset for this route. XRP uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Scroll source 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.

EVM-to-EVM execution boundary

Scroll and BNB Chain 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.

Mistakes specific to WETH Scroll to XRP BNB Chain

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; treating a wrapped token as the native gas asset. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Private Route for WETH → XRP

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 WETH on Scroll to XRP 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 WETH deposit and XRP 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

Swap WETH on Scroll to XRP on BNB Chain FAQs

What exactly leaves Scroll as WETH?

WETH is a contract representation on Scroll with 18 decimals at 0x5300000000000000000000000000000000000004. ETH, not WETH, 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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.

What exactly arrives on BNB Chain as XRP?

XRP is a contract representation on BNB Chain with 18 decimals at 0x1D2F0da169ceB9fC7B3144628dB156f3F6c60dBE. BNB, not XRP, 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. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Why does the WETH to XRP direction matter?

WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

What changes between the source and destination asset roles?

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

What should be matched before sending WETH?

WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. 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. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.

Can the wrapped asset pay native network gas?

No. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. 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.

What funds the Scroll source transaction?

ETH is the native gas asset for Scroll. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WETH is token-tracked and can need approval before transfer.

Can I swap WETH on Scroll to XRP on BSC without KYC?

Requirements are checked for the live WETH Scroll to XRP BSC 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 →