Yesterday, we celebrated EIP-6963 getting the green light.
Today, we’re announcing the release of Web3Modal v3.1, which is now stable and launches as web3’s first modal to support EIP-6963!
This means that, starting today, apps can offer their users the seamless browser wallet connection experience enabled by EIP-6963, which is already supported by more than 10 wallets. Read on to further explore just what exactly this means.
Web3Modal v3.1: Web3’s first modal to support EIP-6963
EIP-6963 was created to solve a specific problem: the poor, often-unpredictable browser wallet connection experience endured by web3 users with multiple installations. It does so by essentially creating a new channel of communication between apps and browser extension wallets, which allows for multiple such wallets to coexist and make themselves available to dapps and other web-based apps.
Not only does EIP-6963 help users easily use and manage multiple browser extension wallets, but it also allows apps to make the connection experience clearer by automatically displaying the wallet’s name and logo in the UI. This is because EIP-6963 gives wallets the opportunity to inject more information, such as the wallet name, logo, UUID, and RDNS.
How does this translate into the Web3Modal experience? For starters, we’ve adjusted the wallet connection interface to showcase a user’s browser extension wallet installations from the get-go. Users can therefore instantly view the browser extension wallets available to them when clicking “Connect Wallet” on an app and choose the one they want to proceed with.