Bitcoin UTXO and account-chain boundary
Scroll uses a non-UTXO source model while Bitcoin uses a UTXO destination model. Native Bitcoin deposits require a supported Bitcoin address, confirmation-aware input handling, and attention to change outputs; an EVM token labeled BTC or WBTC is not native BTC.
Bitcoin receipt-side execution
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays destination-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation 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.
Leaving Scroll L2 for Bitcoin L1
Scroll inclusion and its ethereum settlement are distinct from final receipt on Bitcoin. 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 Bitcoin output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Scroll to Bitcoin bridge mistakes
Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Bitcoin; running out of ETH before the source transaction is submitted; assuming evm and bitcoin 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 Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.