Bridge LINK from Scroll to zkSync Era

FromScroll
TozkSync Era
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

Scroll → ZKsync Era

Asset

LINK

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the LINK asset and Scroll network you currently hold.

2. Review the route

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

LINK source representation

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 is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.

Scroll to zkSync Era L2 handoff

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

LINK destination representation

Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on zkSync Era. The zkSync Era 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 receipt-side execution

zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on zkSync Era. EVM 0x account address A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

Scroll deposit-side 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.

Scroll to zkSync Era bridge mistakes

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for zkSync Era; running out of ETH before the source transaction is submitted. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. 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 LINK → LINK

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

Related routes

Scroll to ZKsync Era FAQs

What LINK representation leaves Scroll?

LINK is a contract representation on Scroll at 0x548c6944cba02b9d1c0570102c89de64d258d3ac. ETH, not LINK, 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. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.

What LINK representation arrives on zkSync Era?

LINK is a contract representation on zkSync Era at 0x52869bae3e091e36b0915941577f2d47d8d8b534. ETH, not LINK, pays gas unless both symbols are the same. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.

Does the same LINK ticker guarantee the same ledger form?

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

Which gas balances matter for this bridge?

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 zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. 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 Scroll address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge LINK from Scroll to ZKsync Era without KYC?

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