DynamicContextProvider’s walletConnectors array (EthereumWalletConnectors, SolanaWalletConnectors, and so on). The JavaScript SDK replaces that array with extensions: for each chain you install its package and call add<Chain>Extension(client) once, right after you create the client and before you use it. Each extension registers that chain’s wallet providers and network support.
Enabling a chain
Enabling a chain is the same call whether or not you use React — add each extension to the client right after you create it:dynamicClient to DynamicProvider (see Basic setup).
What maps to what
addEvmExtension() bundles the EIP-6963 browser-wallet discovery and the embedded (WaaS) EVM provider, so a single call covers both external and embedded EVM wallets. On Solana, add addPhantomRedirectSolanaExtension() alongside addSolanaExtension() when you need the Phantom mobile redirect flow.
Per-chain reference
Each chain’s own setup, supported wallets, and network configuration are documented in the JavaScript reference — start with Adding extensions, then the page for your chain:See also
- Basic setup — create the client the extensions attach to
- Using connected wallets — read the wallets an extension provides
- Network management — switch and validate networks
- Gas sponsorship & smart wallets — the ZeroDev extension for account abstraction