SODAX for Phantom
https://phantom.comMajor unlocks for Phantom
@sodax/sdk swap module
Users swapping between the networks Phantom already supports get cross-network execution routed through SODAX under the hood, removing the manual bridge step from inside the Phantom swap flow.
@sodax/sdk money market module
Phantom users with idle balances can lend directly from their wallet UI, earning yield on assets they hold across Solana, Ethereum, Arbitrum, and other supported chains without leaving the app.
Key observations
Phantom has built something rare: a self-custodial wallet that doubles as a full trading and spending surface, with perps, prediction markets, a Visa debit card, and scam detection baked in at the product layer. The friction point is execution fragmentation across the networks Phantom supports: moving or swapping value between them still requires bridging steps that interrupt the otherwise smooth in-app experience.
The cross-network bottleneck
A Phantom user holding USDC on Ethereum who wants to open a perp or enter a prediction market on a different network today hits a bridge interface before they can act. That context switch erodes the "one home for your money" promise Phantom has built its brand around. Each manual bridge step is a drop-off point for an otherwise engaged user.
The bottleneck isn't asset availability. It's that moving value between the networks Phantom supports requires leaving the flow Phantom spent years making frictionless.
Where SODAX fits
SODAX becomes the cross-network execution rail Phantom calls inside its own swap and trading flows. When a user initiates a swap or a deposit across two of the networks Phantom already supports, SODAX coordinates routing, settlement, and execution recovery behind that action. The user signs a familiar transaction in Phantom. SODAX handles everything underneath. No bridge UI surfaces, no abandoned flows.
Phantom keeps the UX. SODAX absorbs the cross-network execution layer beneath it.
Recommended integration path
- What changes: Swap and cross-network transfer actions inside Phantom's trading and cash flows call SODAX's execution layer via
@sodax/sdkor the React hooks in@sodax/dapp-kit, replacing or augmenting current bridge routing. - What you keep: The full Phantom product surface, including wallet UX, perps, prediction markets, Terminal, and the Visa debit card flow. No product rearchitecture.
- Engineering effort: TypeScript-only integration using
@sodax/dapp-kitswap and money market hooks. No programs to deploy, audit, or maintain. SODAX's programs on Solana are already live and independently audited. Phantom's existing Solana wallet signing works as-is.
Similar protocol using SODAX
Hana Wallet integrated SODAX to power cross-network swaps inside a self-custodial wallet, removing the bridge step from the in-wallet trading flow. The pattern maps directly: same swap module, same money market surface, same wallet-native signing experience.
Next technical discussion
The most useful starting point is scoping which Phantom flow benefits most immediately: the in-app swap router (where SODAX replaces a bridge hop between supported networks) or the money market surface (where idle wallet balances earn yield from inside the app). Confirming Phantom's current swap routing architecture and how @sodax/dapp-kit hooks would sit alongside existing calls would let us define a tested integration surface in one session.
20-minute agenda: map Phantom's swap and transfer flows against SODAX execution paths, identify the first integration point, and agree on a deliverable for a working prototype.
Summary
Product today
Phantom is a multi-chain self-custodial money app with 20M+ users, covering trading, perps, prediction markets, and a Visa debit card.
SODAX angle
Power cross-network swaps and idle-balance lending inside Phantom's existing flows without surfacing a bridge interface.
Let's talk integration
Phantom's in-app swap flow and Perps surface are the natural first home for cross-network execution via SODAX. Let's map out where it fits.
Get in touch
Drop us a message and we'll take it from there.