It spends discrete UTXOs rather than debiting an account balance. Input selection creates outputs and often change, confirmation depth matters to the provider, and a native receiving address must match the Bitcoin address types accepted by the active route. The deposit is a Bitcoin transaction funded by selected inputs; BTC network fees and change outputs are part of the source record before DAI can be delivered on Ethereum.
Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph. The live route must identify native BTC explicitly; a BTC ticker on another chain can represent a wrapped or bridged token.
The provider sets the required Bitcoin confirmation depth. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Bitcoin confirmations and Ethereum transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Ethereum; running out of BTC before the source transaction is submitted; assuming bitcoin and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract; confusing native BTC with wrapped or tokenized Bitcoin. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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.
DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. The destination wallet must support the exact Ethereum representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. 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.
Bitcoin is classified as a UTXO-native asset for this route. BTC uses a native asset on Bitcoin. Native BTC exists on one recorded origin network; other network forms require representation checks. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
Bitcoin UTXO inputs, outputs, change, and confirmation history remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this BTC on Bitcoin to DAI on Ethereum path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats and destination-side EVM 0x account address; it does not hide either chain's public records.
The Bitcoin side uses native BTC and the UTXO ledger. Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph.
The provider waits for its required source confirmation depth. The account-chain transaction and the Bitcoin transaction are separate records.
An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
BTC is listed as the native representation on Bitcoin; BTC is used for network gas. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
DAI is a contract representation on Ethereum at 0x6b175474e89094c44da98b954eedeac495271d0f. ETH, not DAI, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. On receipt, 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.
BTC is the deposited native-asset input; DAI is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Requirements are checked for the live BTC Bitcoin to DAI Ethereum 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.
