# Vote Needed: Resolve ENS Names on L2 chains - Feature Requests - MetaMask

Source: https://community.metamask.io/t/resolve-ens-names-on-l2-chains/28781
Kiwi News: https://news.kiwistand.com/stories/Vote-Needed-Resolve-ENS-Names-on-L2-chains-Feature-Requests-MetaMask?index=0x661e6699108f7fdbc7a38211ac21664fff3aaeb11f54c45dae846022b1ff2dce4c638a68
Submitted by cap.eth on 2024-04-16 UTC, 1 upvote, 0 comments

## Summary

A feature request asks MetaMask to resolve ENS names and subnames on L2 chains such as Optimism, Arbitrum and Base, which the browser extension and mobile wallet currently do only on Ethereum mainnet. The proposer argues that L2 chains' growth in liquidity, dapps and developer activity makes this important for the industry and for easier transacting between wallets. The proposal would use ENS contracts on Ethereum Mainnet as the source of truth regardless of the connected chain, and the author offers to connect the Namespace and MetaMask teams if needed.

## Article

Resolve ENS Names on L2 chains

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: