Investigate reverse resolution edge case

[lightwalker-eth]

---

• Address: 0x60dbf50076206f60bcc2edf9295f5734561b8d77
• ENS Manager App Link: https://app.ens.domains/0x60dbf50076206f60bcc2edf9295f5734561b8d77
• NameGuard Report: https://nameguard.io/inspect/estmcmxci.eth
• Raffy's Resolver Link: https://adraffy.github.io/ens-normalize.js/test/resolver.html#0x60dbF50076206F60bCc2Edf9295f5734561B8d77

---

In the screenshots above, note how we are not displaying a primary name for this address in ENSAdmin. This ENSAdmin screenshot was taken from the Vercel Preview environment on #1291 where protocol acceleration was activated.

Then note how the ENS Manager App screenshot says that this name is not normalized. If that were true then it would explain why we don't return a primary name for it. However, note the NameGuard report showing that the name is actually normalized. Very strange.

For further debugging, see the link to Raffy's Resolver above. Here his resolver reflects the name being normalized also.

Something strange seems to be happening here for us to investigate.

---

Edit: Reviewing the ENS Protocol Inspector in ENSAdmin reveals what I expect to be the issue:

https://app.ens.domains/estmcmxci.eth

Here we can see that the forward resolving ETH address for this name is 0x703ae03fB120eC91e9Ed6d08Ce8044E498CC789B which of course would cause reverse resolution to fail due to the mismatch.

So then the open questions here are:

1. Why does the official ENS Manager App show this error? It seems to be a bug in their app? The name is normalized, it just doesn't have reverse resolution properly configured. This error really threw me off and motivated the creation of this issue.
2. Why doesn't Raffy's Resolver App display an error for this mismatch?

[shrugs]

ok for this person, the address 0x60dbF50076206F60bCc2Edf9295f5734561B8d77 reverses to estmcmxci.eth but the name estmcmxci.eth has an eth addr record of 0x703ae03fb120ec91e9ed6d08ce8044e498cc789b so the reverse resolution fails. this is operating correctly as far as i can ascertain.

the 0x703ae03fb120ec91e9ed6d08ce8044e498cc789b reverse name reverses correctly to estmcmxci.eth and the reverse resolution passes because the addresses match

no idea why the manager app says that estmcmxci.eth isn't normalized, it seems fine to me. correct that resolution is misconfigured and perhaps their app just renders the error incorrectly.

regarding raffy's website, it does disclose the mismatch, just not very loudly

[shrugs]

btw, the ens-app-v3 error code is wrong because that's just how it's coded — any mismatch results in an error saying the name isn't normalized, which is why it's so confusing

https://github.com/ensdomains/ens-app-v3/blob/5541991ed43fa7b39b483d8910e39b6528f19210/src/components/ProfileSnippet.tsx#L331

closing as everything working as intended on our side