Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Scroll. The recorded Scroll 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.
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 Polygon representation. The route converts a wrapped-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Scroll inclusion and its ethereum settlement are distinct from final receipt on Polygon. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Polygon. The recorded Polygon representation uses 18 decimal places. 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.
Polygon is a L1 EVM network in the Polygon ecosystem. POL pays destination-side network gas on Polygon. EVM 0x account address A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.
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.
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 Scroll. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Polygon; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract; treating a wrapped token as the native gas asset. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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.
Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Scroll to DAI on Polygon path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.
WBTC is a contract representation on Scroll with 8 decimals at 0x3C1BCa5a656e69edCD0D4E36BEbb3FcDAcA60Cf1. ETH, not WBTC, pays gas unless both symbols are the same. A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
DAI is a contract representation on Polygon with 18 decimals at 0x8f3Cf7ad23Cd3CaDbD9735AFf958023239c6A063. POL, not DAI, pays gas unless both symbols are the same. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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.
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, 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.
WBTC is the deposited wrapped-asset input; DAI is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. 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 must match the quoted Polygon representation. A ticker or target price is not enough to identify a token contract.
No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.
Requirements are checked for the live WBTC Scroll to DAI Polygon 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.
