You will need to set your ENS primary name to use most Ethereum dApps. Setting your ENS Primary Name will ensure that your .locker name is shown in dApps that use the ENS resolver.

Note that an ENS Primary Name is different from your .locker app Primary Name. A primary name in the .locker app is the main .locker digital identity you will use for transactions. Setting your ENS primary name allows you to use your .locker name with Ethereum apps and digital wallets.

Before You Start

• Make sure you have an Ethereum digital wallet or an Ethereum address in the .locker app.
• You will need Ether for gas on the Ethereum network. For more information on how to buy Ether, contact your digital wallet provider.
• View a comprehensive primary name guide from ENS here.

Set Your ENS Primary Name on Mainnet

This will make your desired .locker name your default on Mainnet.

1. Open the ENS App and connect your digital wallet. The connect button is in the upper right hand corner on app.ens.domains.
2. Select your desired primary name by following the prompts from ENS.
3. You may be asked to update the ETH address for your .locker name. If this happens, it means the digital wallet you're trying to connect is different from the digital wallet currently listed as the owner or controller of that ENS name. Only confirm the address update if you want to change which wallet controls the name.

If your primary name is properly set, you will see your .locker name instead of the standard digital wallet address in dApps that use ENS.

Troubleshooting

The ENS app shows "invalid name" or "no eligible names", or the "Set as a primary name" button is greyed out.

Try: reconnecting your digital wallet or refreshing the page. Because .locker names are stored offchain with ENS, it can take a few minutes to sync.

Your .locker name was set successfully, but still doesn't appear on an Ethereum dApp.

Try: waiting a while and trying again to give the resolver and the blockchain time to sync. If it still doesn't work, confirm that the dApp is integrated with the ENS resolver. If the dApp isn't integrated with the ENS resolver, it is incompatible with .locker. The most popular dApps should not have this problem.