Network
Explore Fetch swap routes
Review the routes that start from or settle to Fetch, with network-aware context around compatibility, costs, and wallet expectations.
Supported assets: 1
Assets you can send: 1
Assets you can receive: 1
Live routes: 5
Best for: Network-aware routes
Fee profile: Route-dependent
Coverage mix: Full send + receive coverage
Use when: Wallet compatibility matters
Route timing: ZyroShift shows the live estimate inside the swap flow, because completion time changes with the exact pair, market path, and destination confirmations.
What is Fetch used for in swap routes?
Fetch appears in routes where the network itself changes how the swap should be evaluated, especially around wallet compatibility, transfer expectations, and the type of ecosystem the user is entering or leaving.
On a hub page like this, the role of Fetch is to make those infrastructure choices explicit so users can decide whether this rail fits their wallet, next app, and cost tolerance before creating a route.
How Fetch changes a swap
Fee profile
Route-dependent
Fetch changes how network cost should be evaluated, so live route details still need to be checked before sending funds.
Compatibility
Fetch-specific
This network matters when the receiving wallet or next application expects Fetch specifically.
Wallet fit
Network-aware
The selected wallet and destination app still need to match the network rail shown on the route.
Best fit
Infrastructure-specific routes
Use Fetch when network compatibility itself is part of the decision, not just the token.
Explore common routes
Use these shortcuts to jump into the most common swap paths tied to Fetch.
Routes you can start on Fetch
Routes you can receive on Fetch
Settle on Fetch when the destination wallet or next app expects FET on this network.
Settle on Fetch when the destination wallet or next app expects FET on this network.
Settle on Fetch when the destination wallet or next app expects FET on this network.
Popular assets on Fetch
How Fetch compares with other networks
Ethereum offers a different balance of cost, compatibility, and ecosystem fit than Fetch.
TronTron offers a different balance of cost, compatibility, and ecosystem fit than Fetch.
BNB Smart ChainBNB Smart Chain offers a different balance of cost, compatibility, and ecosystem fit than Fetch.
SolanaSolana offers a different balance of cost, compatibility, and ecosystem fit than Fetch.
Start a swap on Fetch
Open the live builder, choose the asset that matches your wallet, and keep the selected network explicit before you create the shift.
FAQ
Why use Fetch routes instead of another network?
Fetch matters when the receiving wallet, cost profile, or next app makes this network a better fit than other supported rails.
Do Fetch routes change fees and compatibility?
Yes. That is the core reason network hub pages exist: the network can change transfer cost, wallet expectations, and settlement behavior even when the token symbol stays the same.
Can I send from an exchange to a Fetch route?
Only if the exchange supports the exact network shown on the route page. The withdrawal rail must match the route instructions exactly.
What should I verify before using a Fetch route?
Check the live route details, make sure the wallet supports Fetch, and verify that the send and receive sides match the network shown before sending funds.