Skip to main content

Set your primary name (ENS Explorer)

Set the name apps display instead of your address, from your name's Address Resolution page in ENS Explorer.

Your primary name is the name apps show instead of your address: it's what makes 0x1234…5678 appear as yourname.eth. Setting it links your address back to your name (reverse resolution). For how it works, see What is a primary name?

The Default row covers every EVM chain. The other rows are optional overrides, one chain each.

Steps

  1. Open your name's page and go to Address Resolution. You'll see one row per network: Default, Ethereum Mainnet (the row reads Mainnet), and the L2s, such as Optimism, Arbitrum and Base.

  2. Connect the wallet that can edit the name's records, with a little ETH for network fees (gas). That is the wallet you registered with, unless you gave the role to someone else (see Grant resolver 'roles' to edit name records). On the Default row, select More.

  3. If the saved Address is empty or not yours, check the box holds your wallet address and select Save. Select Start, then Open wallet, and approve.

  4. If the panel says the address does not resolve back to this name, select Set primary name. Select Start, then Open wallet, and approve.

The Address Resolution page in ENS Explorer for bright-lemur.eth, with an empty Default row, an Ethereum Mainnet address and a More button on each row
The Default resolution panel in ENS Explorer, with the Address box and the Save button
The Default resolution panel warning that the set address does not resolve back to this name on Default, with Set primary name

Why there are two steps

A primary name only works when both directions line up. Your name has to point at your address: that is the address you save in step 3. And your address has to point back at your name: that is the primary name you set in step 4.

If the address is set but your wallet doesn't point back, the row's Reverse match shows False. Once both are set, it shows True. If one half is already done, you only need the other step.

Diagram: bright-lemur.eth points to the wallet through its ETH Address and Default address, and the wallet points back to bright-lemur.eth as its Ethereum Mainnet and Default primary name.

If you set your primary name in the ENS App

The ENS App sets your primary name on the Default and Mainnet rows, but it gives your name only an ETH Address, plus the same address on any EVM chains you add. It never fills in the Default row's address. So that row is empty, and on the Reverse Resolution page, other EVM chains show False and Unverified. To fix it, do step 3 above on the Default row. You don't need step 4.

Checking it worked

In your address page's Reverse Resolution section, the row you set shows your name with Forward match: True and a Primary name tag.


Common questions

Do I need to set a primary name for every network?

No. The Default row covers all of them. Set a specific network's row only if you want a different name shown there.

When would I set a different name on a specific network?

Two common cases:

  • Separate identities. You use one name for Ethereum Mainnet activity and another for L2 activity, and want each network to show the right one.

  • Chain-specific apps. Some wallets and explorers check for a network-specific primary before falling back to Default.

If none of these apply, set Default and stop. To set one, follow the steps above on that network's row instead of Default.

What happens if I set both Default and a network row?

The network row wins on that chain. Because a different chain can point at a different address, it can also carry a different primary name.

The Address Resolution page in ENS Explorer for onshow.eth. The Default, Mainnet and Arbitrum rows read True with a Primary name tag. The Optimism, Base, Linea and Scroll rows read Unverifiable. Arbitrum, Optimism, Base and Scroll each hold their own address.

I've approved the transactions — why does the row still show False?

The table reads from an indexer that can run behind the chain. If your transactions have confirmed, wait and refresh before treating it as a failure. If it still shows False after that, the forward record is the usual cause; see Why there are two steps above.

Did this answer your question?