Bridge DAI from Scroll to Base

FromScroll
ToBase
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 → Base

Asset

DAI

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the DAI asset and Scroll network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Base 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Scroll to Base L2 handoff

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

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.

Base receipt-side execution

Base is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Base. EVM 0x account address A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Scroll to Base bridge mistakes

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Base; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. DAI leaves through its network-specific stablecoin contract and can require approval; the collateral design does not make a bridged DAI contract canonical. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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

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

Related routes

Scroll to Base FAQs

What DAI representation leaves 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 source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. 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 Base?

DAI is a contract representation on Base with 18 decimals at 0x50c5725949A6F0c72E6C4a641F24049A917DB0Cb. ETH, not DAI, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 Base can prevent normal detection or receipt.

Can I bridge DAI from Scroll to Base without KYC?

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