Bridge DAI from Scroll to Solana

FromScroll
ToSolana
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 → Solana

Asset

DAI

Source gas

ETH

Destination gas

SOL

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 Solana 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

Convert the Scroll 0x input into a Solana-account receipt

Scroll uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. DAI uses DAI contract token on the source; DAI uses DAI contract token on Solana.

Solana token-account check for DAI

Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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. A compatible wallet may create or use an associated token account, and SOL—not DAI unless it is SOL—pays later Solana fees.

Scroll approval and gas before the handoff

ETH is the native gas asset for Scroll. DAI is contract-tracked and can require an allowance before transfer. 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 keeps its ticker while changing ledgers

Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Scroll. The recorded Scroll representation uses 18 decimal places. The Scroll side is contract-tracked rather than a native gas balance. Native DAI exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make DAI contracts interchangeable across networks. Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. The Solana side is contract-tracked rather than a native gas balance. Native DAI exists on one recorded origin network; other network forms require representation checks. The dollar-oriented ticker does not make DAI contracts interchangeable across networks. DAI leaves as a network-specific contract asset. DAI arrives as a network-specific contract asset.

Scroll to Solana bridge mistakes

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable; 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 Solana account, token, program, signature, and fee activity remain public. For this DAI on Scroll to DAI on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana 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 → Solana
  • Shows what remains public on Scroll and Solana before you deposit
Check Private Route availability →

Related routes

Scroll to Solana FAQs

Can the Scroll 0x account be reused as the Solana destination?

No. Base58-encoded Solana account address ETH pays the EVM source transaction, while SOL is used for later Solana activity.

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 Solana?

DAI is a contract representation on Solana with 8 decimals at EjmyN6qEC1Tf1JxiG1ae7UTJhUxSwk1TCWNWqxWV4J6o. SOL, not DAI, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The bridge output does not automatically fund every later gas need.

What destination address should be used?

Base58-encoded Solana 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 Solana can prevent normal detection or receipt.

Can I bridge DAI from Scroll to Solana without KYC?

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