Swap BNB on zkSync Era to LINK on Scroll

FromzkSync Era
ToScroll
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.
LINK / 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 zkSync Era. The recorded zkSync Era 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.

zkSync Era to Scroll L2 handoff

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

Scroll destination execution

Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Scroll. EVM 0x account address A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll.

LINK output identity and receiving

Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Scroll. The Scroll side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

zkSync Era source execution

zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on zkSync Era. EVM 0x account address A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.

EVM-to-EVM execution boundary

zkSync Era and Scroll 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 BNB zkSync Era to LINK Scroll

Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Scroll; running out of ETH before the source transaction is submitted. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

Private Route for BNB → LINK

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

Related routes

Swap BNB on zkSync Era to LINK on Scroll FAQs

What exactly leaves zkSync Era as BNB?

BNB is a contract representation on zkSync Era with 18 decimals at 0x7400793aAd94C8CA801aa036357d10F5Fd0ce08f. ETH, not BNB, pays gas unless both symbols are the same. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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 Scroll as LINK?

LINK is a contract representation on Scroll at 0x548c6944cba02b9d1c0570102c89de64d258d3ac. ETH, not LINK, pays gas unless both symbols are the same. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

Why does the BNB to LINK 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, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

What changes between the source and destination asset roles?

BNB is the deposited native-asset input; LINK 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 zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

What funds the zkSync Era source transaction?

ETH is the native gas asset for zkSync Era. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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 zkSync Era, or using an address that is not valid for Scroll, can prevent detection or delivery. Match both network labels and representations to the active route.

Can I swap BNB on zkSync to LINK on Scroll without KYC?

Requirements are checked for the live BNB zkSync to LINK Scroll 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 →