Skip to main content
Welcoming cross-network users means supporting the wallets they already use. On Arbitrum, that is any EVM wallet that can sign on Arbitrum One (chain ID 42161), such as MetaMask or Rabby. On the networks your users arrive from, it is Phantom, Suiet, Lobstr, and more. SODAX gives you both through one interface, so wallet plumbing never becomes the integration.

React apps: @sodax/wallet-sdk-react

The React package wraps each chain family’s native wallet SDK (wagmi for EVM networks, including Arbitrum) behind a uniform connector interface with a single persisted store.
Mount the provider with the chains you serve. Arbitrum is an entry under EVM, alongside any other EVM network you support:
Then connect and read accounts with the same three hooks for every chain family:
One EVM connection covers every EVM network, so the wallet may be on a different network than Arbitrum when your user acts. useEvmSwitchChain({ xChainId: ChainKeys.ARBITRUM_MAINNET }) returns isWrongChain and a handleSwitchChain callback to prompt the switch.

Bridging to SDK calls

useWalletProvider({ xChainId: ChainKeys.ARBITRUM_MAINNET }) returns a typed IEvmWalletProvider ready to pass into any @sodax/sdk method. The swap and money market calls take it directly.

Scripts and backends: EvmWalletProvider

Outside React, construct the provider from @sodax/wallet-sdk-core directly:
EvmWalletDefaults lets you tune behavior per provider: sendTransaction, waitForTransactionReceipt, publicClient, walletClient, and transport.