I am curious, why are we not using window.evmproviders , coupled with a great frontend library, EIP5749 can be a better solution
Adding to what Pedro said, the initial idea of using events was to make sure no wallet was left behind since there might be a delay until the injection happens. This is currently managed by individual wallet events or a setTimeout (which isn’t ideal).
I also agree that evmproviders seems more fragile and easier to break. Regarding the iframe security concern, I think we could add an advise on the security considerations section about sandboxing any iframe used in the website. At least on the dapp side the issue will persist whether we use events, window.ethereum, postMessage or anything that’s attached to the window object.
If I’m not mistaken, sandboxing the iframe, as long as the allow-same-origin flag is not there, will prevent the iframe from overwriting the window object.
Hey everyone, me and Boidushya from WalletConnect collaborated on an example dapp that supports EIP-6963
It will detect any EIP-6963 compatible browser wallet and display them. Plus you can connect multiple in parallel and it will display the chain and the accounts
But since there aren’t any in production, we added a button to “emulate” window.ethereum as EIP-6963 provider by wrapping it into an announceProvider event
Also the word “wallet” should not be used in the standard. the assumption that every crypto browser extension is wrong. blockchain based account systems can be anything but a wallet. See UniversalProfiles for example. Yes it can be a wallet, but it’s a lot more than that.
Hey Authors of EIP-6963, congrats on a successful twitter space advocating more adoptions.
We are starting a recurring virtual meetup for ERC authors and dApp builders to meet and talk to each other, advocate for adoption and / or give tech feedback. And we would like to invite you to come over to give a sharing on allercdevs. The event occurs bi-weekly and rotates between two timezone friendly slots, for information go to GitHub - ercref/AllERCDevs: Meeting Repository for AllERCDevs
I’d also like to tighten up the terminology being used. EIP-6963 is all about the relationship between “Dapps” and “Wallet Providers”. I want to make sure this is reflected clearly throughout the spec.