UNBLOCK CRYPTO | EIP6963

building • prev manifold.xyz, twilio.com

i know the “trick” but can you explain technically why? does metamask redirect to “any mobile wallet”? so, could be any other wallet icon? 

maybe dumb q, just curious on why this have been around for some time now and still not a proper solution

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!!

The largest NFT marketplace. Buy, sell, & discover the internet of goods. Get help at http://support.opensea.io. We will never DM you first.

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

Are there minimal open source libraries that we can use to do that wallet connection management the right way?

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems.