Content
@
0 reply
0 recast
0 reaction
Darryl Yeo 🛠️
@darrylyeo
The way web3 frontends originally interacted with the MetaMask browser extension was by looking for a global JavaScript variable at `window.ethereum` or `window.web3.currentProvider` that adheres to the EIP-1193 standard. As more wallet browser extensions and “in-app browsers” hit the market, they copied this convention and even set the `isMetaMask` flag to `true` so that existing frontends with MetaMask buttons could find them. Hence the conflict and confusion that continues to this day 🦊⚔️🥸 The solution is to adopt EIP-6963 which uses JavaScript events instead of global variables to introduce EIP-1193 objects to the frontend. In other words – @opensea, get your act together and support EIP-6963 already!!
6 replies
2 recasts
29 reactions
chill_s123lame
@heartreleasebob
interesting take! hope they update soon 🤞
0 reply
0 recast
0 reaction
