Working in a Web3 centered company, a lot of my online attention is spent on Twitter (X) - after all, this is where a lot of the people in the community are.

A few days ago, I was browsing the feed when I came across the impressive work that Zerion is doing with their UnblockCrypto campaign.

This campaign aims to promote the adoption of a new Ethereum standard, EIP-6963.

EIP-6963

For those unfamiliar, EIP-6963 (Multi Injected Provider Discovery) is a community-driven standard that introduces an alternative discovery mechanism to window.ethereum.

As written in the EIP document:

Currently, Wallet Provider that offer browser extensions must inject their Ethereum providers (EIP-1193) into the same window object window.ethereum; however, this creates conflicts for users that may install more than one browser extension.

This results not only in a degraded user experience but also increases the barrier to entry for new browser extensions as users are forced to only install one browser extension at a time.

In this proposal, we present a solution that focuses on optimizing the interoperability of multiple Wallet Providers. This solution aims to foster fairer competition by reducing the barriers to entry for new Wallet Providers, along with enhancing the user experience on Ethereum networks.

This is achieved by introducing a set of window events to provide a two-way communication protocol between Ethereum libraries and injected scripts provided by browser extensions thus enabling users to select their wallet of choice.

Realizing the Potential

Upon learning about this standard, I immediately saw an opportunity. At Blockaid, we pride ourselves on partnerships with major players like Metamask, Coinbase Wallet, Rainbow, and Zerion.

My idea? Use EIP-6963 to provide social proof to our website visitors.

By highlighting that the wallets they use are likely already compatible with Blockaid, we can build trust and assure them of their choice of us as their security provider—the same idea that is powering our messaging around the Blockaid Network.

The Integration Process

Integrating support for this standard was surprisingly easy. The injected providers that support EIP-6963 publish a window event with a simple interface providing necessary information, including the provider's name and icon.

With this interface, the integration is very straightforward - all you need to do is to listen for window events that contain a provider announcement, make sure that the announced provider is one of our supported providers (list of our customers that integrated EIP-6963 into their extension), and set the state of the banner:

// Listener for wallet provider announcements
window.addEventListener("eip6963:announceProvider", (event) => {
    const {name, icon} = event.detail.info;
    if (Object.keys(supportedProviders).includes(name)) {
      setProvider(supportedProviders[name]);
    }
});

As you can see, the code listens for provider announcements and updates our website to reflect the connected provider, offering a seamless user experience. And the result? Stunning.

Conclusion

EIP-6963 is more than just a technical improvement—it’s a trust signal, a marketing asset, and a way to reduce friction for users navigating the Web3 ecosystem.

By showcasing compatibility with this standard, we’re not just improving UX; we’re reinforcing security, credibility, and seamless integration with the wallets users already trust.

For any crypto project looking to boost adoption, leveraging new standards like EIP-6963 isn’t just a technical decision—it’s a strategic one.

And in an industry where trust is everything, small details like these can make a big difference.

A special mention to this Metamask repository for being an invaluable resource during this process.