Direction
Base → Bitcoin
Asset
DAI → BTC
Source gas
ETH
Destination gas
BTC
Choose the DAI asset and Base network you currently hold.
Check the estimated output, fees, timing, and Bitcoin destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Base 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 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.
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Base. EVM 0x account address A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.
Base 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.
The live quote lists the exact Base input asset and Bitcoin output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Route-specific mistakes include sending on a network other than Base; 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 Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
Base wallet, token-transfer, contract, log, and gas activity remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this DAI on Base to BTC on Bitcoin path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats; it does not hide either chain's public records.
Bitcoin is the UTXO destination and requires a supported Bitcoin address. Tokenized BTC on an account chain is not the same ledger asset.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Bitcoin output before depositing.
A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress. The bridge output does not automatically fund every later gas need.
Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats Do not substitute a Base address merely because a wallet displays both networks.
Sending on a network other than Base, selecting a representation not listed by the quote, or entering an address invalid for Bitcoin can prevent normal detection or receipt.
Requirements are checked for the live DAI Base to Bitcoin 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.
