Skip to main content
Welcoming cross-network users means supporting the wallets they already use. On Solana that is Phantom, Backpack, Solflare, and anything else speaking the wallet-standard; on the networks your users arrive from, it is MetaMask, Rabby, Suiet, Lobstr, and more. SODAX gives you both through one interface, so wallet plumbing never becomes the integration.
Using the HTTP API? You sign and broadcast the intent transaction yourself (see the bot flow), so these wallet packages are optional. This page covers SDK wallet integration.

React apps: @sodax/wallet-sdk-react

The React package wraps each chain family’s native wallet SDK (@solana/wallet-adapter for Solana) behind a uniform connector interface with a single persisted store.
Mount the provider with the chains you serve. Chains are opt-in; add Solana with an RPC endpoint:
Then connect and read accounts with the same three hooks for every chain family:

Bridging to SDK calls

useWalletProvider returns a typed ISolanaWalletProvider ready to pass into any @sodax/sdk method. The swap and money market calls take it directly. A headless useWalletModal state machine is available if you are building a multi-chain connect modal.

Scripts and backends: SolanaWalletProvider

Outside React, construct the provider from @sodax/wallet-sdk-core directly:
SolanaWalletDefaults lets you tune Solana-specific behavior per provider: connectionCommitment, connectionConfig, sendOptions, and confirmCommitment.