Loading route...
Swap>
Swap WBTC to BTC
Route overview
SWAPWBTC to BTC
This route converts wrapped BTC exposure into native Bitcoin, changing the terminal position from chain-specific BTC representation into direct BTC settlement. The source asset is wrapped BTC exposure rather than native BTC, so the route includes an additional layer of chain-specific representation risk. The destination asset is native Bitcoin, so the terminal settlement profile is oriented around direct BTC ownership rather than application-layer utility.
Non-custodialLive routeNetwork-aware routing
Route note: this page is prefilled with WBTC on Ethereum, while WBTC is currently supported across 6 send networks on ZyroShift.
Route profile
Use this route when wrapped BTC exposure needs to be unwound into native BTC settlement rather than retained inside another chain environment. This profile is generally associated with moving BTC-linked value out of wrapped liquidity and into a different settlement context. This profile is generally associated with allocating value into native BTC settlement rather than maintaining exposure inside another token environment.
Send
WBTC on Ethereum
Receive
BTC on Bitcoin
Live swap card
Swap WBTC to BTC with the route prefilled.
Current rate
Select a valid pair to fetch a live variable rate
You send
Network
Select network
Variable rate creates the shift first. The shift page shows the deposit range before funds are sent.
You receive
NetworkSelect network
Live unit rate
--
Current live rate before the shift is created.
Deposit rule
[warning] Select a pair to see the live min and max deposit range before you create the shift.
Status note
After you create the order, the app redirects to a dedicated shift screen with the QR code, countdown, waiting state, and live status polling.
Live route context
Builder first, then route-specific timing and limit context.
Send
WBTC on Ethereum
The route starts with the exact deposit asset and network selected for this page.
Receive
BTC on Bitcoin
Settlement is sent to the destination asset and network defined by this route.
Timing
Provider-driven
Timing depends on deposit detection, route processing, and confirmation-sensitive settlement before BTC lands on Bitcoin.
Deposit limits
Live minimums
Minimums and maximums are route-specific, so the builder and final shift page remain the source of truth before funds are sent.
How this swap works
1
Choose WBTC as the asset you send and BTC as the asset you receive.
2
Confirm the route starts on Ethereum and settles on Bitcoin before creating the shift.
3
Enter a BTC receiving wallet that matches the destination network exactly.
4
Create the shift, follow the deposit instructions, and track settlement until BTC lands on the destination side.
Route-specific notes
Wrapped BTC assets do not settle like native BTC on every rail, so both the send context and the BTC destination details should be verified carefully.
This route relies on a compatibility-oriented rail, which generally implies broader wallet support and more predictable address handling.
The receiving wallet format matters on this route, so the destination address should be checked against the exact chain shown in the builder.
Native settlement routes require close attention because the destination is expected to settle directly on its base network rather than as a wrapped representation.
Confirmation-sensitive settlement can extend total route duration relative to a single fast-transfer path, particularly when native delivery is involved.
Related routes
Reverse route
Looking for the reverse path?
Move in the opposite direction while keeping the same pair context available from a dedicated route page.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Explore tokens and networks
Explore WBTC routes
View routes where WBTC is the asset being sent or received.
Explore BTC routes
See more swap paths that settle into BTC.
Explore Ethereum routes
Review routes that start from the Ethereum network.
Explore Bitcoin routes
See destinations and routes that settle on Bitcoin.
Explore Altcoin to BTC routes
Move up one level and review the full altcoin to btc routes family instead of a single route only.
Compare Stablecoin to BTC routes
Review the adjacent stablecoin to btc routes family when the next decision could change the destination or landing intent.
Pair FAQ
Why do users swap WBTC to BTC?
This route is commonly used when a wrapped BTC representation is being converted back into native BTC settlement.
Why is this route described as compatibility-first?
Because the selected network is chosen primarily for wallet support and address-format predictability rather than for minimum transfer cost alone.
Why does wallet format matter on this route?
Because the destination asset can settle correctly only when the receiving wallet matches the exact chain and address format required by the selected route.
What does native settlement mean on this route?
It means the destination asset is expected to settle on its native network rather than as a wrapped representation on a different chain.
Why can timing vary on this route?
Because completion depends on deposit detection, provider routing, and final chain confirmations rather than on a single transfer event.
Route disclaimer
Rates, minimums, and maximums are provider-driven and can change before the shift is created.
Always verify the deposit instructions on the shift page before sending funds.
The selected receiving network must match the destination wallet and asset route.
For WBTC to BTC, the live builder and shift page remain the final source of truth.