You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metamask is used by pretty much everyone, but the current Web3Provider standards don't account for multiple providers.
There are dApps that would like to specifically with the Safe (at least slow.trade, Olympia).
The current "hacky" overwrite solution is not 100% reliable.
Acceptance criteria
There are 2 ways, the dApps could be integrate with the Safe extension:
Way 1: Communicate with extension via injected Web3Provider
If no other provider installed:
If website not whitelisted: do nothing
If website is whitelisted: inject (EIP-1102)
If other provider installed
Display info/error message to the user that there is another one and that will cause problems. (Same like Metamask)
How will this message be displayed? Console first, some other UI perhaps later
Way 2: Communicate with extension via channel other than the injected provider
For dApps that want to integrate specifically with the Safe, no matter if the user has a Safe or not.
Still respect whitelisting toggle, i.e. only allow communication when site (dApp) is whitelisted.
→ The Safe extension will only be usable, (1) if there is no other provider available or (2) if the dApp specifically integrates with it via some kind of library.
The text was updated successfully, but these errors were encountered:
Story
As a user I am able to use the Gnosis Safe with dApps on my browser so I can make use of my funds.
Background
Acceptance criteria
Way 1: Communicate with extension via injected Web3Provider
Way 2: Communicate with extension via channel other than the injected provider
→ The Safe extension will only be usable, (1) if there is no other provider available or (2) if the dApp specifically integrates with it via some kind of library.
The text was updated successfully, but these errors were encountered: