Bridge LINK from Base to Scroll

FromBase
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.

Direction

Base → Scroll

Asset

LINK

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the LINK asset and Base network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Scroll 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 Base. The Base 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.

Base to Scroll L2 handoff

This route crosses two L2 execution environments. Base settles to ethereum, while Scroll 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 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.

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

Base deposit-side execution

Base is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Base. EVM 0x account address A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.

Base to Scroll bridge mistakes

Route-specific mistakes include sending on a network other than Base; using a destination that is not valid for Scroll; running out of ETH before the source transaction is submitted. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 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 LINK → LINK

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

Related routes

Base to Scroll FAQs

What LINK representation leaves Base?

LINK is a contract representation on Base at 0x88fb150bdc53a65fe94dea0c9ba0a6daf8c6e196. ETH, not LINK, pays gas unless both symbols are the same. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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 Scroll?

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.

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 Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. 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. 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 Base address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge LINK from Base to Scroll without KYC?

Requirements are checked for the live LINK Base to 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 bridge FAQs →