
THORSwap users have access to Chainflip's liquidity pools through its cross-chain routing engine. Following community proposal TIP-15, THORSwap now operates as an independent, multi-chain DEX aggregator powered by SwapKit, not as a frontend for any single protocol. Its routing layer queries Chainflip alongside other native cross-chain liquidity sources, then picks whichever delivers the best execution for each swap.
This isn't just another aggregator partnership. It reflects how cross-chain swap interfaces are evolving away from single-protocol dependence toward true meta-aggregation across native liquidity sources.
How THORSwap Routes Through Chainflip
THORSwap's smart routing layer queries Chainflip's pools as part of every swap quote, alongside the other native cross-chain protocols it supports. The Chainflip integration is one of several that feed the same routing engine.
When you request a swap on THORSwap, the interface compares quotes across all the protocols it aggregates. The routing logic factors in the total cost: swap fees, network fees, slippage, and execution time. Whichever route delivers more output tokens to your destination address wins.
The decision happens automatically. Users don't need to manually select which protocol to use or understand the differences between each routing source. The interface abstracts this complexity away.
When Does THORSwap Choose Chainflip?
The routing decision depends on several factors that shift constantly based on market conditions. Chainflip typically wins the route in specific scenarios.
Mid-Size Native BTC Swaps
Chainflip's JIT (Just-in-Time) liquidity model allows market makers to provide precise quotes for incoming swaps. For native Bitcoin trades in the mid-size range, this often results in tighter spreads than continuous-curve AMM pools.
For trades that don't need to be split across time, Chainflip's JIT model can execute faster than alternatives that rely on streaming or batching to manage price impact.
Specific Asset Pairs
Liquidity depth varies across protocols. Chainflip might have deeper pools for certain pairs like SOL/BTC or ETH/BTC at any given time. THORSwap's routing engine detects these imbalances and routes accordingly.
Network Congestion Periods
When one routing source experiences high volume or network delays, routing to the alternative can mean faster confirmation times. This redundancy benefits users who need reliable execution regardless of conditions on any single network.
Technical Differences in Execution
Understanding why Chainflip sometimes offers better execution requires looking at the architectural differences across cross-chain swap protocols.
Many native cross-chain protocols use continuous liquidity pools where prices follow a bonding curve. Large swaps move the price, and the slippage compounds as trade size increases. Some protocols mitigate this with streaming swaps that split large trades over time, trading latency for execution quality.
Chainflip combines AMM pools with JIT market makers who can provide custom quotes. When a swap request arrives, market makers compete to fill it with the best price. This competition mechanism often produces tighter execution, especially when liquidity providers are actively managing positions.
Across the protocols THORSwap aggregates, assets remain native. Your BTC stays as BTC throughout the swap process, secured by validators in a decentralized custody model rather than a centralized custodian.
Concrete Swap Scenarios
To illustrate when each routing source might win, consider these examples.
Scenario: Native BTC to SOL
A user wants to swap native Bitcoin for Solana. THORSwap queries every protocol it routes through. Chainflip's JIT market makers return a quote with lower slippage because active LPs are competing for the flow. THORSwap routes through Chainflip.
Scenario: Large ETH to BTC Swap
A whale wants to move a significant amount of ETH to BTC. Some routing sources handle this with streaming swaps that break the order into smaller chunks over several minutes to reduce price impact. THORSwap's engine factors these features in and may route the trade where it produces the most output, or split it across multiple protocols.
Scenario: USDC Cross-Chain Transfer
Moving stablecoins between chains often involves minimal price risk but variable fees. The routing engine compares total costs including network fees on each chain. The winner depends on current gas prices and pool depths.
What's Next: Metro
THORSwap is rolling out a new flagship product called Metro, currently in beta at metro.exchange. Pitched as a Bitcoin-first DeFi superapp, Metro brings the same SwapKit-powered routing engine into a redesigned interface that adds lending, yield, and a built-in self-custody wallet alongside swaps.
For users, the practical impact is that Metro inherits THORSwap's integration with Chainflip. When you swap through Metro, the routing logic still pulls from Chainflip's liquidity pools when execution is best there. The interface changes; the access to native cross-chain liquidity does not.
For Chainflip liquidity providers, Metro represents another funnel of demand. A more polished consumer interface sits on top of the same aggregation layer that already routes through Chainflip.
What This Means for Users
For THORSwap users, the integration is largely invisible. You get better execution on more swaps without changing your workflow. The competitive pressure between routing sources benefits the broader ecosystem by incentivizing every protocol in the routing pool to improve their liquidity and pricing.
For liquidity providers, the integration creates more flow for Chainflip pools. Swaps that would otherwise route through other protocols now have a chance to land on Chainflip when the pricing is competitive. This increased volume benefits LPs earning fees on Chainflip.
The integration also demonstrates a maturing approach to cross-chain infrastructure. Rather than winner-take-all competition, multiple protocols can coexist and route flow based on who serves each specific swap best. This is how traditional financial markets work, and crypto is catching up.
How This Differs from Generic Aggregator Integrations
You might wonder how the THORSwap integration differs from Rango Exchange routing through Chainflip. The key difference is depth of integration and scope.
Rango operates as a broad aggregator across bridges, DEXs, and cross-chain swappers, many of which use wrapped tokens or custodial intermediaries. THORSwap focuses specifically on native cross-chain protocols where assets move in their original form, which means tighter integration with the smaller set of protocols that share that design.
This focus lets THORSwap weigh factors like confirmation times and settlement finality that generic aggregators might not prioritize as heavily.
Looking Ahead
The THORSwap integration reflects a broader trend toward interoperability between native cross-chain protocols. As Chainflip continues adding new chains and assets, the routing options available to THORSwap and Metro users keep expanding.
For users, this means more options and better pricing. For the protocols, it means healthy competition that drives improvement. And for the cross-chain swap category overall, it demonstrates that collaboration can coexist with competition.
Try a swap on THORSwap or the Metro beta and watch which protocol handles your trade. The routing transparency lets you see exactly when Chainflip liquidity powers your cross-chain transaction.
Resources
Swap Now - Start swapping native assets
Lend BTC - Borrow against native Bitcoin
Blog - Product updates and announcements
Chainflip Scan - Track swaps and network activity
Website - Explore Chainflip
Other Chainflip Products:
Boost - Earn fees by providing single-sided liquidity with no IL risk
Stablecoin Strategies - Deposit stablecoins and earn optimized yields
Provide Liquidity - Supply assets to Chainflip's liquidity pools
Stake FLIP - Delegate FLIP and earn staking rewards
Find us:
What is the THORSwap Chainflip integration?
THORSwap routes swaps through Chainflip's liquidity pools when they offer better execution than other native cross-chain protocols it aggregates. The routing happens automatically based on which source delivers the best price for each specific swap.
When does THORSwap route through Chainflip?
THORSwap chooses Chainflip when it offers better pricing, typically for mid-size native BTC swaps, specific asset pairs with deeper Chainflip liquidity, or during periods of congestion on other routing sources.
Do I need to do anything different to use Chainflip through THORSwap?
No. The integration is automatic. THORSwap's routing engine compares the protocols it supports and selects the best route without requiring any user input or configuration.
Are my assets still native when routed through Chainflip?
Yes. Chainflip handles native assets without wrapping. Your BTC, ETH, SOL, and other assets remain in their native form throughout the swap process.
What is Metro and how does it relate to THORSwap?
Metro is THORSwap's new flagship product, currently in beta at metro.exchange. It is a Bitcoin-first DeFi superapp built on the same SwapKit-powered routing engine, which means Metro inherits THORSwap's integration with Chainflip and routes through Chainflip whenever Chainflip offers the best execution.
How does this integration benefit liquidity providers?
LPs on Chainflip gain access to additional swap volume from THORSwap and Metro users. When Chainflip wins the routing competition, that flow generates fees for Chainflip liquidity providers.

