How to Set an ENS Wallet Address Record

To connect an ENS name to a receiving wallet, set its address record in the official ENS App. For the Ethereum Mainnet destination, edit the ETH Address field. For other supported chains, add the appropriate chain record. Setting a receiving address and choosing a wallet’s primary display name are separate configuration tasks.

Understand which setting you need

Do not use the name’s Owner field as evidence of where a payment will arrive. Before changing anything, write an expected result: “For this name, this chain and this app, the receiving address should be this full address.” It gives you a specific acceptance test.

Set or change the Ethereum address

The official ETH-address instructions use the following path:

1. Open app.ens.domains and connect the wallet permitted to edit the name.
2. Find the full name, open Profile and choose Edit Profile.
3. Enter or update ETH Address using the independently checked destination.
4. Review the proposed change and approve the matching wallet transaction.
5. After confirmation, reopen the profile and compare the complete saved address.

For an unwrapped name, records are controlled by its Manager. Wrapped names merge that role into the Owner. These edits require Ethereum Mainnet gas. If you only need to change display identity, use the primary-name instructions.

Add an address for another chain

In Edit Profile, the documented route is Add more to profile, then Addresses. Choose the intended chain, add its correctly formatted address and review the save. Use the record for the destination network you actually intend to support.

An explicit chain record takes precedence. The current ENS instructions distinguish the Default EVM fallback from ETH Address; they are separate settings. Non-EVM networks need their own relevant record. The existence of a record does not establish that every sending wallet reads it correctly.

Project-issued subnames, including Basenames, are managed through their issuing project’s interface. Do not assume the .eth editing path applies to every name connected with the ENS ecosystem.

A worked acceptance check

Imagine a studio wants a public .eth name to represent its Ethereum receiving wallet, while using a different address for one other supported chain. Its maintainer writes down both full destinations before editing. After confirmation, a second maintainer compares the saved records with that brief.

They then inspect the intended app’s read-only recipient lookup for each relevant network. If the app shows only the beginning and end of an address, they expand the destination before comparing it. They record the app/version, network, name, full result and time checked.

This establishes what that lookup showed. It does not demonstrate a completed transfer, settlement or support in every other app. Our compatibility guide explains these evidence boundaries.

If the edit or lookup fails

• No edit control: check the connected wallet and its record-management permission.
• Old record remains: check confirmation before repeating the change.
• Only one app differs: investigate its supported lookup method and cached data.
• After a purchase or transfer: review all destinations rather than assuming they changed with ownership.

Keep a short diagnostic note instead of changing several settings at once. The troubleshooting guide follows the symptom to the relevant configuration layer.

Keep the public record deliberate

ENS profile records are public, and removing a current value does not erase its historical onchain appearance. Publish receiving addresses intentionally. Avoid adding private contact information simply because the profile form has an empty field.

Update public payment instructions only after checking the new configuration. For team maintenance, keep the person authorized to change records distinct from the person who merely reviews the public result.