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 receiving address must be a Bitcoin address accepted by the active provider. The delivered BTC becomes a UTXO; it is not a token contract or gas balance 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 source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Bitcoin confirmations and Ethereum transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Ethereum; 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; confusing native BTC with wrapped or tokenized Bitcoin. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
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. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this ARB on Ethereum 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.
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.
Destination Bitcoin receipt has its own confirmation progress. The account-chain transaction and the Bitcoin transaction are separate records.
An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
ARB is a contract representation on Ethereum at 0xb50721bcf8d664c30412cfbc6cf7a15145234ad1. ETH, not ARB, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
BTC is listed as the native representation on Bitcoin; BTC is used for network gas. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On receipt, Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
ARB is the deposited token input; BTC is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Requirements are checked for the live ARB Ethereum to BTC 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.
