Bitcoin UTXO and account-chain boundary
Bitcoin uses a UTXO source model while Tron uses a non-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.
Tron receipt-side execution
Tron is a L1 TVM network in the Tron ecosystem. TRX pays destination-side network gas on Tron. Tron Base58Check address, commonly beginning with T A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees.
Bitcoin deposit-side execution
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays source-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth.
Choose an asset that exists on both route sides
The live quote lists the exact Bitcoin input asset and Tron output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Bitcoin to Tron bridge mistakes
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Tron; running out of BTC before the source transaction is submitted; assuming bitcoin and other addresses are interchangeable. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees.