Dan raises a good point.
We indeed have an opt-out feature in our extension, called "Recognizable Connect Buttons". It replaces instances of "injected wallet", "browser wallet" and "Metamask" with "Zerion" for our extension users.
Why do we do that?
We want our users to have a more streamlined "connect wallet" flow. Every dapp works with Zerion, but most of them still hard code Metamask and Coinbase as the only wallet providers, making it confusing for Zerion users to not see a login option with the Zerion button.
What is the problem & our plan?
Unfortunately, overriding the text in web pages in not perfect, and sometimes leads to inaccurate replacements. Our plan is to completely remove this feature once we have most dapps/connect kits supporting the new EIP-6963.
What is EIP-6963?
Thanks to
@pedrouid, EIP-6963 aim to finally solve the issue of conflicting browser extensions, allowing users to use multiple wallets at the same time. It is already adopted by many wallets (including MM), but still lacks support in ConnectKits and even top dapps.
Competition & fairness
Dan called this feature anti-competitive. Naively, I never thought of it this way. I believe users should be able to browse permissionless Web3 with wallets they love & use. But I appreciate the Metamask team for guarding our space from unfair competition.
How do you feel about web3 wallet extensions that replace instances of their competitors' names with their own in pages you browse? (Very tacky innovation,
@zerion)