- Limit which chain wallets are available — via
walletProvidersConfig - Provide credentials for WalletConnect, TON, or Immutable Passport — via
walletDefaults
Coming from the self-bundled Widget? The
walletProviders prop and createEVMProvider()-style factories do not exist in @layerswap/widget-react. See Self-bundled Widget or the migration guide.Filtering chains
UsewalletProvidersConfig to limit which chain wallets users can connect:
includekeeps only the listed wallet types;excluderemoves the listed wallet types.
WalletProviderId):
Supplying credentials
Some wallet services need your own credentials or metadata. Pass them viawalletDefaults:
object
Your WalletConnect Cloud
projectId (required for WalletConnect connections) plus optional app metadata (name, description, url, icons) shown in the wallet’s connection prompt.object
TON wallet support configuration. Both
tonApiKey and the manifestUrl of your TON Connect manifest are required. TON wallets appear only when this object is supplied.object
Immutable Passport client configuration.
publishableKey, clientId, redirectUri, and logoutRedirectUri are all required. Immutable Passport appears only when this object is supplied.Sharing your wagmi config
If your app already uses wagmi for EVM wallets, pass yourConfig as the wagmiConfig prop and the widget adopts it — same connected account, same chain, no second connect flow. This replaces the old “Partial Integration (EVM)” setup and has its own page:
Sharing your wagmi config
Reuse your app’s EVM wallet connection inside the widget