# Well-known extensions

**URL:** <https://community.metamask.io/t/well-known-extensions/29037>\
**Category:** Feature Requests\
**Created:** [June 1, 2024, 6:33pm UTC](https://community.metamask.io/t/well-known-extensions/29037 "2024-06-01T18:33:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikita.k](https://avatars.discourse-cdn.com/v4/letter/n/ea666f/32.png) [@nikita.k](https://community.metamask.io/u/nikita.k)\
**Post date:** [June 1, 2024, 6:33pm UTC](https://community.metamask.io/t/well-known-extensions/29037/1 "2024-06-01T18:33:00Z")

</div>

**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:

 ![Screenshot 2024-06-01 at 21.11.34](https://europe1.discourse-cdn.com/metamask/original/3X/c/5/c588538e55b9c806eeb18379643e8ca27784b660.png)

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:

 ![Screenshot 2024-06-01 at 21.30.33](https://europe1.discourse-cdn.com/metamask/original/3X/8/2/829e11d696b96062278c9b10e1a523225c943d50.png)