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 Polygon.
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. WBTC follows a smart-contract ledger and must not be sent to a native Bitcoin address.
The provider sets the required Bitcoin confirmation depth. EVM 0x account address A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Bitcoin confirmations and Polygon transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Polygon; using a destination that is not valid for Bitcoin; running out of POL before the source transaction is submitted; assuming evm and bitcoin addresses are interchangeable; confusing native BTC with wrapped or tokenized Bitcoin; treating a wrapped token as the native gas asset. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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.
WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC is the source token on Polygon. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
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.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Polygon. The recorded Polygon representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
Polygon wallet, token-transfer, contract, log, and gas activity remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this WBTC on Polygon 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.
A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.
WBTC is a contract representation on Polygon with 8 decimals at 0x1BFD67037B42Cf73acF2047067bd4F2C47D9BfD6. POL, not WBTC, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
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.
WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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.
WBTC is the deposited wrapped-asset 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 WBTC Polygon 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.
