Direction
Tron → Bitcoin
Asset
BTC
Source gas
TRX
Destination gas
BTC
Choose the BTC asset and Tron network you currently hold.
Check the estimated output, fees, timing, and Bitcoin destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Tron uses a non-UTXO source model while Bitcoin uses a UTXO destination model. Native Bitcoin deposits require a supported Bitcoin address, confirmation-aware input handling, and attention to change outputs; an EVM token labeled BTC or WBTC is not native BTC.
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays destination-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
Tron is a L1 TVM network in the Tron ecosystem. TRX pays source-side network gas on Tron. Tron Base58Check address, commonly beginning with T A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution.
The live quote lists the exact Tron input asset and Bitcoin output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Route-specific mistakes include sending on a network other than Tron; using a destination that is not valid for Bitcoin; running out of TRX before the source transaction is submitted; assuming other and bitcoin addresses are interchangeable. A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress.
Tron address, token-transfer, contract, and resource activity remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this BTC on Tron to BTC on Bitcoin path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Tron Base58Check address, commonly beginning with T 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.
Bitcoin is the UTXO destination and requires a supported Bitcoin address. Tokenized BTC on an account chain is not the same ledger asset.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Bitcoin output before depositing.
A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. A Bitcoin destination creates a UTXO at a supported Bitcoin address; later spending pays a BTC miner fee and begins new confirmation progress. The bridge output does not automatically fund every later gas need.
Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats Do not substitute a Tron address merely because a wallet displays both networks.
Sending on a network other than Tron, selecting a representation not listed by the quote, or entering an address invalid for Bitcoin can prevent normal detection or receipt.
Requirements are checked for the live BTC Tron to 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.
