Description:
MetaMask is a nice and pleasant UX when a web page connects to MM for querying accounts and requesting users to confirm transactions.
However, it is not that pleasant when a different chromium extension attempts to connect. Instead of showing a nice name, MM shows an extension ID. Like so:
It would be super nice for users, as well as for web3 developers, including developers of other blockchain protocols if it was possible to display a proper name. Obviously, it would not be safe if a connecting app could simply specify a name to present to users — that would open a lot of phishing opportunities.
To mitigate the phishing risks while still providing this capability, the MM team could arrange the notion of “well-known extensions”. With this notion, the MM extension, detecting an incoming connection from a different extension, could consult with a publicly-available database (e.g., a JSON file hosted under the MM repository) and use a therein-specified name, falling back to extension ID if the extension is not “well-known”.
A development team could then send an application to the MM team to register their extension ID in the list of well-known extensions.
Purpose:
Better UX for both users and developers.
Extension/Mobile/Both:
Extension
Seems like this is the place for it:
