Bridge DAI from Linea to Scroll

FromLinea
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

Linea → Scroll

Asset

DAI

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the DAI asset and Linea 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

DAI representation on both sides

DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path. The same stablecoin ticker does not make the two network records or contracts interchangeable.

ETH source gas and ETH destination readiness

A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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.

Linea to Scroll L2 handoff

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

Linea deposit-side execution

Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Linea. EVM 0x account address A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones.

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.

Linea to Scroll bridge mistakes

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for Scroll; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. 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 receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Private Route for DAI → DAI

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

Related routes

Linea to Scroll FAQs

What DAI representation leaves Linea?

DAI is a contract representation on Linea with 18 decimals at 0x4AF15ec2A0BD43Db75dd04E62FAA3B8EF36b00d5. ETH, not DAI, pays gas unless both symbols are the same. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical.

What DAI representation arrives on Scroll?

DAI is a contract representation on Scroll with 18 decimals at 0xcA77eB3fEFe3725Dc33bccB54eDEFc3D9f764f97. ETH, not DAI, 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. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.

Does the same DAI ticker guarantee the same ledger form?

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

Which gas balances matter for this bridge?

A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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 Linea address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge DAI from Linea to Scroll without KYC?

Requirements are checked for the live DAI Linea 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 →