BNB is classified as a native asset for this route. BNB uses a quote-selected representation. Native BNB exists on multiple recorded origin networks; other network forms require representation checks. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a quote-selected representation. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
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 destination token. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and the selected destination network addresses, transfers, amounts, fees, and timing remain public. For this BNB on BNB Chain to WBTC on the selected destination network path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side the selected destination network address; it does not hide either chain's public records.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
BNB is the deposited native-asset input; WBTC is the quoted wrapped-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. Match the source network shown by the quote. Confirm the destination network in the quote. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
No. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Requirements are checked for the live BNB BNB to WBTC Wrapped 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.
