Native Bitcoin swaps on Phantom
Ecosystem
Phantom users have always been able to buy, swap, and trade across Solana and EVM chains inside the wallet. Bitcoin was the exception. Not because demand wasn't there; but because native BTC execution is different.
Phantom integrated Garden's API to solve it. The result: native Bitcoin swaps directly inside one of crypto's most used wallet.
The opportunity
Wallets have quietly become the most strategically important surface in crypto. They're where users spend time, build habits, and make decisions.
Phantom is where Solana lives for most users. Over 10 million wallets. Deep liquidity across SPL tokens, EVM assets, and stablecoins. For the SOL ecosystem, it's the default interface. For a generation of users whose first crypto experience was on Solana, Phantom is the starting point.
But the asset that represents $1 trillion+ in held value and remains the first thing most people think of when they think about crypto was missing. Phantom's users could hold Solana assets, trade across most chains, and manage stablecoins. But if they wanted Bitcoin, they had to look elsewhere: a CEX, a separate bridge, a different product.
Bitcoin access inside the wallet meant keeping users inside the ecosystem they'd already chosen. It meant wallet to wallet BTC settlement without custody, without redirects, without friction. The question was how to enable it without compromising the experience.
Integration
Phantom integrated Garden's API as the Bitcoin execution layer, slotting it into their existing swap routing stack. Phantom handles everything users see and touch, the interface, the quote comparison, and the wallet experience. Garden handles moving native Bitcoin across chains without taking custody of it.
When a Phantom user initiates a SOL to/fro BTC swap, they're interacting with Phantom. Underneath, Garden's solver network is settling the swap atomically via HTLCs; cryptographic contracts that guarantee the exchange completes in full or reverts entirely.
Order flow
- User initiates a swap inside Phantom; SOL to BTC or BTC to SOL
- Phantom's router queries Garden's API for a live quote alongside other available routes
- When Garden wins on price and speed, Phantom calls the Garden API to initiate the order
- A Garden solver locks the matching asset on the destination chain; user locks source asset in an HTLC contract
- The atomic swap executes. The user receives native BTC or SOL directly in their Phantom wallet
By the numbers
Phantom went live in February 2026. On day one, users completed 234 swaps totaling $249K. No incentive program. No launch campaign. The demand was already sitting inside the wallet.
Since launch, 13,892 unique Phantom users have swapped native Bitcoin through Garden, settling over $12M in total volume across 18,560 swaps. The completion rate currently stands at 99.8%. Phantom users expect the same reliability from a Bitcoin swap that they get from any other trade in the wallet.
Why Garden
Built for Bitcoin's architecture, not around it
Bitcoin's UTXO model, its finality characteristics, and HTLC based settlement require a purpose built execution layer. Garden is designed specifically around how Bitcoin works on L1. That's what makes sub 30 second settlement possible, and it's what makes the reliability numbers hold at scale.
Non-custodial at the protocol level
For a wallet with 10M+ users, custody risk isn't acceptable at any point in a swap flow. Garden never holds user funds. HTLCs enforce settlement cryptographically: the swap completes atomically or the user's funds return.
Reliability that matches consumer expectations
99.8% completion across 18K+ swaps. Of the 0.2% that didn't complete, 70% were AML screening blocking order initiation on the solver side. This means Phantom could ship native Bitcoin with the same confidence it applies to every other asset class it supports.
One integration, full Bitcoin execution
Phantom added native Bitcoin routes through a standard API integration. No solver to run, no liquidity pools to seed, no separate settlement infrastructure to maintain.
Last updated