EVM to Solana route mechanics
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.
Solana receipt-side execution
Solana is a L1 SVM network in the Solana ecosystem. SOL pays destination-side network gas on Solana. 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.
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.
Leaving Scroll L2 for Solana L1
Scroll inclusion and its ethereum settlement are distinct from final receipt on Solana. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
Choose an asset that exists on both route sides
The live quote lists the exact Scroll input asset and Solana output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
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. 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.