Stargazer’s Integration of EIP-6963: Bridging the Gap Between Wallets and DApps
Stargazer is excited to announce its upcoming implementation of the EIP-6963 standard. This is a significant step in our commitment to enhancing user experience and interoperability with EVM dApps.
This integration aims to facilitate more straightforward use of Stargazer with DApps already compatible with EIP-6963.
Users can look forward to a streamlined experience with DApps such as Uniswap, Yearn, and Etherfi, with expectations for broader adoption across the ecosystem.
How will the EIP-6963 introduction benefit Stargazer wallet users?
EIP-6963 proposes a standard that helps websites using Ethereum or other EVM networks more efficiently discover and connect with various crypto wallets that users might have installed in their browser. This means that when you use a website that interacts with Ethereum, it can automatically recognize all your compatible wallets, making it more straightforward to choose which one you’d like to use for transactions or interactions on that site.
If you have multiple wallets, you may have noticed that when you interact with a DApp, one of your wallets automatically connects to it, often without giving you a choice. DApps detect and connect to Ethereum wallets, which can lead to a frustrating experience if you don’t intend to use the auto-selected wallet.
Also, each DApp you encountered might have required a specific, sometimes cumbersome integration process to connect with your wallet of choice, such as Stargazer Wallet.
This has led to a situation where not all DApps support your preferred wallet
Let’s consider a practical scenario to illustrate this improvement:
Imagine you have both Stargazer Wallet and another popular wallet like MetaMask installed.
In the past, when visiting a new DApp, you might have found that it only offered direct support for MetaMask.
Now, with EIP-6963, when you visit a DApp, it will detect all compatible wallets installed in your browser, including Stargazer Wallet. The app’s interface will give you a choice, allowing you to select Stargazer Wallet for your session if you prefer its features or have specific assets you want to use.
Users can choose their preferred wallet based on features, security, or where their assets are stored rather than restricted by the DApps’ specific integrations.
For Stargazer Wallet users, this means unprecedented accessibility and ease of use, enabling a wide array of DApps without waiting for or relying on integration efforts from each DApp to support Stargazer.
Important Update and Migration Details for Developers
To support EIP-6963, we were required to update the Stargazer wallet web browser extension. This update introduced some changes that required updating our Stargazer connector, including breaking changes affecting all existing websites/applications that integrate with Stargazer.
The breaking changes
In the current version of Stargazer (v4.1), the wallet activation process was initiated the first time the provider received a request() call. This meant that executing:
window.stargazer.getProvider(‘ethereum’).request({ method: “eth_accounts”, params: [] })
would trigger the Stargazer pop-up, prompting the user for wallet access permission.
In the next version of Stargazer (v5), we have updated the wallet activation process.
The wallet activation pop-up will only appear if you specifically call dag_requestAccounts on the Constellation provider or eth_requestAccounts on the Ethereum provider. Alternatively, you can activate the wallet using the activate() method, which utilizes the aforementioned methods internally.
Migration Instructions:
1- For integrations utilizing the Stargazer Connector:
- Update Stargazer Connector to v3 (https://github.com/StardustCollective/stargazer-wallet-connector)
2- For integrations, directly using the window.stargazer object
- If using eth_accounts, you will need to use eth_requestAccounts from now on
- One of two ways:
- Make an RPC call to either eth_requestAccounts or dag_requestAccounts.
- Invoke the activate() method (a single time is sufficient) on any provider, whether it be “constellation” or “ethereum”.
We highly recommend integrating the Stargazer Connector to streamline the update process and ensure optimal compatibility.
Support and Timeline
Stargazer v5 will be available to the public in the week of May 20th.
We urge all teams to update their integrations immediately to avoid disruptions. Our team is available on Discord to assist if you encounter any issues or have questions.
Sepolia and discontinuing Goerli
Support for the Sepolia network will be available on our next Stargazer release before v5, with plans to phase out Goerli in the forthcoming update Stargazer v5. This approach allows us to maintain a broad network support base while preparing for Goerli’s eventual discontinuation in a future update.
Resources for Stargazer’s upgrade
Stargazer Connector v3
- https://www.npmjs.com/package/@stardust-collective/web3-react-stargazer-connector
- https://github.com/StardustCollective/stargazer-wallet-connector
Documentation and Support
Stargazer Documentation
EIP-6963 Standard
Developer Support:
