# Resolve ENS Names on L2 chains

**URL:** <https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781>\
**Category:** Feature Requests\
**Created:** [April 16, 2024, 11:36am UTC](https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781 "2024-04-16T11:36:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thecap.eth](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.io/thecap.eth/32/35378_2.png) [@thecap.eth](https://community.metamask.io/u/thecap.eth)\
**Post date:** [April 16, 2024, 11:36am UTC](https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781/1 "2024-04-16T11:36:05Z")

</div>

**Description:**

Both browser extension and mobile wallet resolve ENS names only on the Ethereum mainnet. However, the L2 chains on MetaMask don’t support ENS resolution - the biggest Web3-native decentralized naming system in the world.

Considering the L2 chains’ mission of scaling Ethereum and their exponential growth in liquidity, ecosystem dapps, and developer activity, it’s important for the entire industry that MetaMask supports ENS name and subname resolution on L2 chains for easier transacting between wallets and improving Web3 identity overall, as the industry-leading wallet, and set a precedent for others.

I propose to implement the functionality to resolve ENS names and subnames across all L2 chains (Optimism, Arbitrum, Base, etc.), utilizing ENS contracts on the Ethereum Mainnet as the source of truth, regardless of which chain the user is connected to.

We are happy to open up a line of communication between the Namespace and MetaMask teams to make this process smoother if necessary.

**Purpose:**

The purpose is to have ENS functionality working on L2 chains which are being used more and more every day.

**Extension/Mobile/Both:**

Both.

**Images/Attachments:**

---

<div class="post-metadata">

**Author:** ![Jaredfromsubway](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.io/jaredfromsubway/32/36059_2.png) [@Jaredfromsubway](https://community.metamask.io/u/Jaredfromsubway)\
**Post date:** [June 7, 2024, 11:05pm UTC](https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781/2 "2024-06-07T23:05:43Z")

</div>

Good propose. It’s time integration more, becouse it’s best ever tools on blockchain. Better then BAYC or cryptopunks.

---

<div class="post-metadata">

**Author:** ![Zimtente.eth](https://avatars.discourse-cdn.com/v4/letter/z/9de0a6/32.png) [@Zimtente.eth](https://community.metamask.io/u/Zimtente.eth)\
**Post date:** [June 8, 2024, 6:20am UTC](https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781/3 "2024-06-08T06:20:02Z")

</div>

This is very much needed! As more and more Communities will create their own L2/L3 subdomain Projects.