Loading route...
Swap>
Swap GRASS to BTC
Route overview
SWAPGRASS to BTC
This route connects two specific crypto assets through the wallet-native swap flow, and the exact asset-plus-network combination remains more informative than a broader family label. The source asset does not fall into the primary route families, so the pair should be evaluated as a more specific asset-to-asset conversion. 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 asset is currently supported through a single send network, so the preset shown here reflects the only available source rail: Solana.
Route profile
Use this route when the exact asset pair matters more than broad BTC, stable-value, or meme-family positioning. This profile is generally associated with a specific transfer or allocation requirement rather than with a broad market-structure trade. This profile is generally associated with allocating value into native BTC settlement rather than maintaining exposure inside another token environment.
Send
GRASS on Solana
Receive
BTC on Bitcoin
Live swap card
Swap GRASS 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
GRASS on Solana
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 GRASS as the asset you send and BTC as the asset you receive.
2
Confirm the route starts on Solana 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
Because this is a long-tail direct route, the live builder and final shift page remain the authoritative source for route definition before funds are sent.
Solana is commonly used when wallet compatibility and standard address behavior are prioritized over the lowest possible transfer cost.
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.
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.
Explore tokens and networks
Pair FAQ
What should I verify before swapping GRASS to BTC?
Verify the send asset, receive asset, destination wallet, and exact network path shown by the live builder, because the route definition is pair-specific.
Why is GRASS to BTC treated as a direct route?
Some token pairs are more accurately described as exact asset-to-asset conversions than as members of a stronger route family. In those cases, the pair definition itself carries the most relevant context.
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.
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 GRASS to BTC, the live builder and shift page remain the final source of truth.