Token
Explore SAI swap routes
Track how SAI appears across supported send and receive routes, with network-aware paths and non-custodial settlement flows.
Category: General crypto asset
Common role: Multi-route crypto asset
Supported networks: 2
Popular routes: 7
What is SAI used for in swaps?
SAI appears in routes where users want to move into, out of, or across the general crypto asset bucket without relying on a custodial exchange flow.
This hub surfaces the supported networks, the strongest send and receive routes, and the intent patterns that show how SAI is actually used inside the broader route graph.
SAI route overview
SAI route pages are strongest when they explain why this asset appears in certain send and receive flows, which networks support it best, and which related routes users commonly choose next. This hub is designed to surface those patterns rather than show a flat list of links.
Supported networks
Each supported network changes cost, compatibility, and wallet expectations. Use the right rail for the wallet or ecosystem you plan to use next.
Liquid is a Bitcoin-sidechain option for users already operating in the Liquid asset environment for SAI routes.
Use when
- - the route needs Liquid wallet compatibility
- - you are already operating in a Bitcoin-sidechain environment
Ethereum is used when ERC20 compatibility and DeFi wallet support matter most for SAI routes.
Use when
- - ERC20 wallet compatibility is required
- - the route will connect to DeFi or EVM apps next
Popular ways to swap from SAI
Altcoins into Bitcoin
Routes that rotate a non-Bitcoin asset into BTC as a more conservative destination.
Altcoins into stablecoins
Routes that exit a volatile asset into SAI for a more stable landing asset.
Between ecosystem assets
Routes that move between ecosystems without using SAI as a stable stop in the middle.
Popular ways to receive SAI
Stablecoins into other ecosystems
Routes that push SAI into another chain or app ecosystem without stopping in a custodial exchange account.
Useful when the user wants to deploy stablecoin value into native SAI on Ethereum (ERC20) for activity in the destination ecosystem.
Stablecoins into other ecosystemsUseful when the user wants to deploy stablecoin value into native SAI on Ethereum (ERC20) for activity in the destination ecosystem.
Bitcoin into other ecosystems
Routes that move BTC into another ecosystem when users need native settlement on the destination chain.
Common route patterns
Altcoins into stablecoins
2
Routes that exit a volatile asset into SAI for a more stable landing asset.
Stablecoins into other ecosystems
2
Routes that push SAI into another chain or app ecosystem without stopping in a custodial exchange account.
Bitcoin into other ecosystems
1
Routes that move BTC into another ecosystem when users need native settlement on the destination chain.
Altcoins into Bitcoin
1
Routes that rotate a non-Bitcoin asset into BTC as a more conservative destination.
More SAI routes
Rotate SAI into Bitcoin when the destination needs native BTC settlement.
Use SAI as the source asset when the route should end in a more stable landing asset.
Use SAI as the source asset when the route should end in a more stable landing asset.
Useful when the user wants to switch ecosystems or rebalance from SAI into ETH while keeping the send and receive flow wallet-native.
Start a SAI swap
Open the live builder, choose the network that matches your wallet, and create the shift from there.
FAQ
What role does SAI play in swap routes?
SAI can appear as a send asset, a receive asset, or both depending on whether users are entering its ecosystem, leaving it, or rotating through it as part of a broader route.
Do I need a dedicated SAI wallet before swapping?
Yes. The destination wallet or address format still needs to match the selected receive network, so the receiving setup should be ready before the route is created.
How do network choices change SAI swaps?
Network choice changes wallet compatibility, transfer cost, and sometimes memo requirements. That is why this hub highlights the supported network rails rather than treating every SAI route as interchangeable.
Can I use SAI in non-custodial swaps without creating an exchange account?
That is the core idea of these routes: the builder sets the pair and network context first, then the shift page handles deposit instructions and status tracking without turning the flow into a custodial exchange workflow.