Connecting Blockchains with Embedded Wallets
Embedded Wallets (formerly Web3Auth) is the frontend authentication system for your dApp. Once the user is authenticated, the SDK returns a way to interact with the blockchain. A provider is how libraries like web3.js & ethers.js talk to the blockchain by sending JSON-RPC requests and receiving responses.
With Embedded Wallets, you can connect in two ways:
- Web (Embedded Wallets Web SDK): You get a MetaMask-style EIP-1193 provider (compatible with ethers.js and web3.js) to submit JSON-RPC requests and interact with the blockchain.
- Mobile (Embedded Wallets Mobile SDK): The user's private key is available in the SDK state, enabling direct signing and lower-level JSON-RPC calls from your app.
The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plug and Play SDKs). Package names and APIs remain Web3Auth (for example, Web3Auth React SDK), and code snippets may reference web3auth identifiers.
Dashboard Configuration
The Embedded Wallets Web SDK(@web3auth/modal) from v10 onwards does not need any additional setup on the code side for blockchain connections. All of it is handled on the Dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
Reference Guides for Blockchain Connections
You can check out the following guides we've written for certain blockchains. We have covered a wide variety of EVM and EVM Chains, supported by multiple Embedded Wallets providers.
