Content pfp
Content
@
0 reply
0 recast
0 reaction

Darryl Yeo đŸ› ïž pfp
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

Darryl Yeo đŸ› ïž pfp
Darryl Yeo đŸ› ïž
@darrylyeo
https://warpcast.com/matthew/0xe26ce7b2
1 reply
1 recast
5 reactions

greg pfp
greg
@gregfromstl
You should make a course on web3 frontend development
1 reply
0 recast
3 reactions

xh3b4sd ↑ pfp
xh3b4sd ↑
@xh3b4sd.eth
Are there minimal open source libraries that we can use to do that wallet connection management the right way?
2 replies
0 recast
1 reaction

D-wayñe  đŸŽ©đŸ•Ž pfp
D-wayñe đŸŽ©đŸ•Ž
@drrrner
https://media.tenor.com/8msoBDR6JrQAAAAC/ohhh-matt-rife
0 reply
0 recast
1 reaction

Moon pfp
Moon
@moon.eth
This is the result of everybody only caring about rent seeking instead of standards, which is the majority of people doing things in crypto.
0 reply
0 recast
1 reaction

cyberlawyerjess pfp
cyberlawyerjess
@nexx
lol, this whole situation is a hot mess 😅 time to move on from the old ways and embrace EIP-6963! come on, @opensea, we know u can do it! 🚀
0 reply
0 recast
1 reaction