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 USDT can be delivered on zkSync Era.
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 A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Bitcoin confirmations and zkSync Era transaction finality are separate milestones.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for zkSync Era; 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. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. The destination wallet must support the exact zkSync Era representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on zkSync Era. The recorded zkSync Era representation uses 6 decimal places. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
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 zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this BTC on Bitcoin to USDT on zkSync Era 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.
A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.
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.
USDT is a contract representation on zkSync Era with 6 decimals at 0x493257fD37EDB34451f62EDf8D2a0C418852bA4C. ETH, not USDT, pays gas unless both symbols are the same. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. On receipt, Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
BTC is the deposited native-asset input; USDT 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 USDT zkSync 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.
