Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap WBTC on Scroll to BTC on Tron

FromScroll
ToTron
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.
BTC / USD
Price
—
24h
—
High
—
Low
—
Vol
—

What you need to know

Scroll to Tron: TRC-20 and EVM boundary

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 Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Scroll and Tron use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.

TRX resources and Tron address check

TRX is the native gas asset for Tron. Tron Base58Check address, commonly beginning with T A TRC-20 token transfer is not an ERC-20 transfer even when an asset ticker exists on both sides.

WBTC to BTC representation change

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination. Verify the exact TRC-20 contract and the Scroll representation independently.

WBTC unwrap or exchange input check

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.

Mistakes specific to WBTC Scroll to BTC Tron

Route-specific mistakes include sending on a network other than Scroll; using a destination that is not valid for Tron; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable; confusing native BTC with wrapped or tokenized Bitcoin; 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 Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.

WBTC input identity and handling

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.

BTC output identity and receiving

Bitcoin is classified as a UTXO-native asset for this route. BTC uses a network-specific contract asset on Tron. The recorded Tron representation uses 8 decimal places. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.

Private Route for WBTC → BTC

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this WBTC on Scroll to BTC on Tron path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Tron Base58Check address, commonly beginning with T; it does not hide either chain's public records.

  • ✓Reduces the obvious link between the WBTC deposit and BTC receipt
  • ✓Compare standard and Private Route options for Scroll → Tron
  • ✓Shows what remains public on Scroll and Tron before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate WBTC to BTC route explainerPrivacy limits and live availabilitySwap BTC to WBTCReverse routeWrapped Bitcoin (WBTC)Bitcoin (BTC)Scroll networkTron networkBrowse supported swap routes

Swap WBTC on Scroll to BTC on Tron FAQs

Is the WBTC or BTC side TRC-20?

The Tron side must match the TRC-20 contract or native TRX label shown in the route. The Scroll side is a separate network representation.

What exactly leaves Scroll as WBTC?

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.

What exactly arrives on Tron as BTC?

BTC is a contract representation on Tron with 8 decimals at TN3W4H6rK2ce4vX9YnFQHwKENnHjoxb3m9. TRX, not BTC, pays gas unless both symbols are the same. 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. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.

Why does the WBTC to BTC direction matter?

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, Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.

What changes between the source and destination asset roles?

WBTC is the deposited wrapped-asset input; BTC is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending WBTC?

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 Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.

Can the wrapped asset pay native network gas?

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 Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees.

Can I swap WBTC on Scroll to BTC on Tron without KYC?

Requirements are checked for the live WBTC Scroll to BTC Tron 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.

View all Help Center FAQs →