Seemingly valid names are being reported as invalid by metadata service

[serenae-fansubs]

This name appears to be valid: https://app.ens.domains/name/%E2%8C%90%E2%97%A8%E2%80%90%E2%97%A8.eth/details

⌐◨‐◨.eth

The eth-ens-namehash.normalize method also doesn't throw any errors:

require("@ensdomains/eth-ens-namehash").normalize('⌐◨‐◨.eth')

⌐◨‐◨.eth

Yet the metadata service is reporting that as invalid: https://metadata.ens.domains/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/29374690480179650074424749477986431727881478513446796185670528844166493337335/image

[schnapseth]

I have the same problem with 𓃵𓃵𓃵.eth
Have you found a solution?

[serenae-fansubs]

When this happens, it appears that the NFT metadata endpoint also returns is_normalized: false.

Are marketplaces like OpenSea/Rarible automatically delisting names because our metadata service is doing this? We have been getting many support tickets in recent days about OpenSea delisting ENS names, when it appears that there's nothing invalid about the name. In some cases this could be due to a human-intervention delisting because OpenSea staff thinks the name is trying to spoof/impersonate some other name.

[mdtanrikulu]

Oh my bad, I need to explain what goes wrong. So the issue is causing because of ens-validation library, which was previously not in use but after adding emoji support to the library I started to use it in ens-metadata-service actively. The reason why I needed that library is to evaluate non-ascii dangerous patterns more precisely.

Later on we started to see some names invalid. The reason for that, while ens-validation library supports full set of emojis, it apparently does not have support for some of b/w symbols. I was working on adding them into the validation library but there is a big issue about that. The "some" I mention above, basically a lot of it. Those symbols are represented as set of symbols, e.g. (Egyptian_Hieroglyphs, Anatolian_Hieroglyphs and many more.) I am still looking into it to grasp how to handle this issue easier, and what is the estimation of those addings. If this gonna take near forever we may revert usage of validation library for now.

[serenae-fansubs]

Thanks for the explanation, that definitely sheds some light!

It looks like it's not just those kinds of symbols, but characters from other more common languages too, like Spanish, Greek, etc. For example, someone reported an issue with this name today: ξlon.eth

ξ is lowercase so ξlon.eth should be a valid and normalized name too, but runs into the same problem:

https://metadata.ens.domains/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/27978210512157853987895129733316778952294480585435466862955698074581821116023

[schnapseth]

Have you reverted yet? Thanks for the explanation.

[serenae-fansubs]

This also appears to be happening with other quite common characters too, like €. For example, someone registered €euro.eth today and it was immediately delisted from OpenSea.

Same thing in the metadata service, it's returning "is_normalized: false": https://metadata.ens.domains/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/75146923466576329054850177628347347164866684791162808436924508302462317903567

require("@ensdomains/eth-ens-namehash").normalize('€euro.eth');

€euro.eth

It's just a guess on my part, but I think that the massive amount of OpenSea delistings we've seen recently are directly tied to our metadata service and the fact that it's incorrectly reporting names as not normalized.

[malikrakhimov]

Hi!
thank you serenae-fansubs for mentioning my problem. Yes, I have registered €euro.eth domain. At first it wasn’t showing on opensea at all. Then, after long conversations with their support team, somehow it managed to show up in my account. But again as “invalid name”.
checked my OS account today, it just disappeared from the list of my NFTs.

Is there any solution for that? Is there anything I can do about it or just wait ?
thank you

[toobusycoding12]

I've spoken to 8 other people and we are also having this issue! I registered a name a few hours ago and the metadata service incorrectly reported it as not normalized again. PLEASE FIX THIS ASAP! It is causing some of my clients who buy from me on OpenSea and Rarible to distrust me!! >:(

[mdtanrikulu]

I made a PR for this issue and it should solve the problem for many names, and I will be sure that mistakenly delisted names on NFT marketplaces will relist them.

However what I see in the discussion, some of the reported names may look valid when you check with normalization library but in actual they are not valid when it comes to domain spoof checking. The new library I introduced does this check properly unlike ens-validation library and in case you are in doubt that the name must be valid, you can make a check manually with the official confusable unicode character list.

One example is ⌐◨‐◨.eth @serenae-fansubs shared.

Here is the quick implementation of spoof check on given name;
https://runkit.com/mdt/ens-confusable

in short, the result is;

'isConfusing'  true
'confusables' [
  { point: '⌐' },
  { point: '◨' },
  { point: '‐', similarTo: '-' },
  { point: '◨' },
  { point: '.' },
  { point: 'e' },
  { point: 't' },
  { point: 'h' }
]
'rectified version' '⌐◨-◨.eth'

'labelhash of original name' '29374690480179650074424749477986431727881478513446796185670528844166493337335'
'labelhash of rectified name' '111440747936573806392167052078801952303595836080754646941339900940965969244004'

Based on this result, if we check opensea with the labelhash of rectified name we see that there is already a valid name with valid characters, so that makes the given name invalid.
https://opensea.io/assets/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/111440747936573806392167052078801952303595836080754646941339900940965969244004

[serenae-fansubs]

Thanks for the updates and work on this!! I definitely appreciate that this is not an easy problem to solve.

At the end of the day, if the manager UI allows a name to be registered, then it should be considered valid in my opinion.

Is this new library also going to be applied to the manager UI too, and will names automatically be redirected to the "rectified" version? Because right now you can search for both ⌐◨‐◨.eth and ⌐◨-◨.eth and different names come up.

And I'm assuming the same changes should be made to ens-eth-namehash too, for its normalize method?

Basically as far as normalization goes, I think it's less important what the actual rules are, and more important that all the places in ENS that use normalization are consistent, and it sounds like they are currently not consistent, which leads to these issues where someone registers a name and then finds out later that they can't use it.

• Manager app UI
  • Searching for a name should yield the normalized/rectified version of that name
  • Going directly to the URL of a non-normalized name should redirect to the normalized version (like ⌐◨‐◨.eth should redirect to ⌐◨-◨.eth)
• The ENS metadata service
• The ENS eth-ens-namehash normalize method, which ENS explicitly recommends client dapps to use for normalizing names

Since it sounds like ENS is changing which names are valid/normalized and which ones aren't, and some people have already registered names through the manager UI that they thought were valid, I'm assuming those people will simply be stuck with unusable/unsellable names, right? Does the ENS core team have any kind of marketing/outreach announcement planned for when this goes live?

Again thanks, I know there is no perfect solution here, and there have been long discussions about this: https://discuss.ens.domains/t/ens-name-normalization/8652/54. Just want to make sure that if we are making this change, that it is made consistent across all the ENS libraries/tools/UI, so that users won't run into this issue again in the future!

[mdtanrikulu]

At the end of the day, if the manager UI allows a name to be registered, then it should be considered valid in my opinion.

Is this new library also going to be applied to the manager UI too, and will names automatically be redirected to the "rectified" version? Because right now you can search for both ⌐◨‐◨.eth and ⌐◨-◨.eth and different names come up.

Yes, definitely that's my aim to do so. This check should be done in wherever we can integrate it.

And I'm assuming the same changes should be made to ens-eth-namehash too, for its normalize method?

Basically as far as normalization goes, I think it's less important what the actual rules are, and more important that all the places in ENS that use normalization are consistent, and it sounds like they are currently not consistent, which leads to these issues where someone registers a name and then finds out later that they can't use it.

* Manager app UI
  
  * Searching for a name should yield the normalized/rectified version of that name
  * Going directly to the URL of a non-normalized name should redirect to the normalized version (like [⌐◨‐◨.eth](https://app.ens.domains/name/%E2%8C%90%E2%97%A8%E2%80%90%E2%97%A8.eth/details) should redirect to [⌐◨-◨.eth](https://app.ens.domains/name/%E2%8C%90%E2%97%A8-%E2%97%A8.eth/details))

* The ENS metadata service

* The ENS [eth-ens-namehash](https://github.com/ensdomains/eth-ens-namehash) `normalize` method, which [ENS explicitly recommends client dapps to use](https://docs.ens.domains/contract-api-reference/name-processing#normalising-names) for normalizing names

Currently the library remains separated from normalization library itself, in the future it might be unified or one can be used in another. But one thing is for sure that both checks needs to be done for consistency whenever we do normalization.

Since it sounds like ENS is changing which names are valid/normalized and which ones aren't, and some people have already registered names through the manager UI that they thought were valid, I'm assuming those people will simply be stuck with unusable/unsellable names, right? Does the ENS core team have any kind of marketing/outreach announcement planned for when this goes live?

Currently it is not yet clear. But in general yes, I believe this will be done at some point.

Again thanks, I know there is no perfect solution here, and there have been long discussions about this: https://discuss.ens.domains/t/ens-name-normalization/8652/54. Just want to make sure that if we are making this change, that it is made consistent across all the ENS libraries/tools/UI, so that users won't run into this issue again in the future!

🙏 Absolutely same thoughts

[toobusycoding12]

Yea that’s what the issue is. We go and register a name for x amount of years just to find out we can’t transact with it on 3rd party marketplaces such as Opensea. There was an instance a few weeks ago where I was going to buy it’s.eth from Opensea and once the seller and I finally came to an agreed upon price it became invalid on opensea and was later removed from the website as a whole. It seems to be happening to many names that have ‘ in them

[timtamjam100301]

yep I have the same issue I bought a domain name is it has been delisted and I contacted opensea and they said its been permanently delisted and I reckon I have such as good domain being ßullish.eth can I please get some help

[Lord-Highfixer]

Hello ENS team. Support sent me here to report on another 3-letter ENS domain that gives "Invalid name" orange background with an exclamation point for:

õ¿ö.eth

On a different issue, I do have this one without any errors but does not display properly. The mouth doesn't appear.

ʕʘ̅͜ʘ̅ʔ

Thank you.

[DIAMONDDOXXED]

Hi ENS.

I'm having trouble with three new names. Same issue. Support forwarded me to you guys:

t≡sla.eth https://app.ens.eth.limo/#/name/t%E2%89%A1sla.eth/details
tξsla.eth https://app.ens.eth.limo/#/name/t%CE%BEsla.eth/details
≡lon.eth https://app.ens.eth.limo/#/name/%E2%89%A1lon.eth/details

From support: "FYI those other two are not using the letter xi Ξ, they are using the mathematical operator ≡. I'm not sure if that mathematical operator will be considered valid in the future, but you may want to ask the devs on that GitHub issue"

Please help and thank you so much!

[Crazyalltnt]

I also have the same issue. I just registered an ens domain name that contains the characters [₿], but I can't use this domain name to transfer money in metamask, I can't see my domain name nft on opensea, os prompts me that it can't be displayed, and I can't use this ens domain name in etherscan Search for the corresponding address.

[rogersmarin]

Same issue here but i have domains with emoji letters (🅰🅱🅲🅳🅴, 🅐🅑🅒🅓🅔) all have been delisted

[serenae-fansubs]

Hey again @mdtanrikulu!

I know the normalization discussion is still ongoing on the forums, but can we expect the metadata service to be reverted in the meantime so that people don't run into the invalid image problem?

Or, should the ENS manager app be updated to not allow the same set of characters that the metadata service currently doesn't allow?

The main issue right now is that people go to the ENS manager website, and it allows them to type in and register a name, and it's only later on that they find out it's invalid. So if this issue isn't going to be resolved anytime soon, would it make sense to at least apply the same normalization changes to the manager UI in the meantime as a stopgap solution?

Thanks!

[ZeroPie]

Hi guys

i registered https://app.ens.domains/name/%E2%80%8D01.eth/details
it was acceptable input in the search bar but it's being marked as an invalid domain

same for:
https://app.ens.domains/name/%E2%97%AF%E2%80%8D%E2%97%AF%E2%80%8D%E2%97%AF%E2%80%8D.eth/details

‍‍I used the Zero Width Joiner

See:
https://adraffy.github.io/ens-normalize.js/test/resolver.html#%E2%80%8D01

[sanskaryo]

👱‍♀‍.eth is not showing on opensea , and invalid on looksrare/ x2y2

It is present on my keyboard, does it has xwz ?

[Ralph89]

I also do have this problem with ◕ω◕.eth

[yoleyo]

can u do somethin to make appear my
https://app.ens.domains/name/1%D0%BE%D0%BE.eth/details
thanks

[nickroels]

I have the same problem. https://app.ens.domains/name/%D0%B7o%D0%B7o.eth/details

[itjustis]

hi! have the same issue with 𓂀𓂀𓂀𓂀.eth :(
https://app.ens.domains/name/%F0%93%82%80%F0%93%82%80%F0%93%82%80%F0%93%82%80.eth/details

[serenae-fansubs]

It looks like this affects Japanese characters too: ミュウツー.eth

https://metadata.ens.domains/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/34543231005394167657646627178145067742716461140010355061808593149089148364942

[topraktepeefe]

It looks like this affects Japanese characters too: ミュウツー.eth

https://metadata.ens.domains/mainnet/0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85/34543231005394167657646627178145067742716461140010355061808593149089148364942

It also affects Turkish characters. İ-Ş-Ü-Ğ

[eddiwoon]

same problem with ens begin with "ß" (german eszet / sharp s)

[ZeroPie]

1. i think having the front throw errors for zero width joiner invalid combinations would be wise, to prevent more invalid domains from piling up.

2. Is there any way to make invalid ZWJ combinations valid by replacing the ZWJ char with another character that OS and Secondary Markets accept as valid?

[joeatang]

Same Challenge happening with me via ens regarding 比心♥️ showing invalid and not being listed on OS - WOuld love for Ens to keep us all updated (play-by-play) via twitter. Thank you!

[Pitter108]

This is answer from opensea customer service

Hi there,  Thanks for reaching out. I apologize for any inconvenience this may have caused. I understand it can be quite confusing if your ENS is not showing at OpenSea. Don't worry, I’d be happy to clarify why your ENS name is not visible on OpenSea.  ENS allows users to register names that are not valid. For example, they may contain zero-width spacing between characters or invalid characters altogether. Because of this, ENS will remove the names once their system identifies them.  It’s important to note that OpenSea doesn’t control ENS — instead, OpenSea is simply a window into viewing what’s currently in your wallet. If ENS removes something or marks it invalid, it’s not something OpenSea can change. We do, however, display a warning message on ENS names that we believe to be at risk of removal.  With that said, if you believe they incorrectly removed or marked your ENS as invalid, we recommend reaching out to them. Once it’s been corrected, OpenSea will start displaying the name again within your wallet.  Here’s the website to contact ENS directly: https://docs.ens.domains/frequently-asked-questions I know this can be confusing, so please let me know if I can help with anything else. Take care! 😊️

[rocketinspirit]

Hey there, I was directed to this page by ENS support on twitter regarding the same issue of having an "invalid" names being delisted or not being visible on Opensea. One of the names I registered contained characters from the Japanese keyboard and others contained emoji's. I received the same message Pitter108 received after contacting Opensea. This is an example of one of the names. https://app.ens.eth.limo/#/name/%E3%82%A8%E3%83%AC%E3%83%96%E3%83%BC.eth/details

I'm glad to know it has been something that is being worked on and there will be a resolution for this soon. It's also helpful to know there is a tool that I can use to check names with non ASCII characters, which I'll try to use in the future.

Good luck!

[Pitter108]

Any update friends? I still didn't receive those registered name.

[toemm]

Having the same issues and found this thread on discord. Payed around 600$ in eth for a 3 character domain which is delisted on Opensea after.. Many people on Discord having this issue for months. A fix or update is needed here before more people lose money...

[Pitter108]

Is there anybody to fix our problem?

[ZeroPie]

This domains

While browsing around on OS i came across this domain and observed it contains an ⚠️
https://opensea.io/assets/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/641843354079041929038989821364773426388122798518459335069695137152283574237

What brought me to the idea of having some sort of flag to make it evident that some domains contain special characters. If i understand correctly os is just trying to prevent scams. What if we had a mechanism to add a flag to differentiate domains with non discernable characters?

This makes them tradeable, this makes them distuinguishable, everyone is happy :)?

[Pitter108]

This is another answer from opensea customer service

Hello,

Thank you for patiently waiting for our response. How are you doing? I hope you are well.

I am very sorry to hear that your ENS domains doesn't show in OpenSea. I understand that this has been frustrating, and I do apologize for the inconvenience it has caused. Rest assured that I will do my best to clarify why your ENS name isn’t visible on OpenSea.

Taking a look at the item’s history, your ENS name was delisted under our Terms of Service, meaning it will no longer appear on our platform. I understand this can be really disappointing.

If an ENS name violates our Terms of Service, or we receive a DMCA request, we may be obligated to remove it from OpenSea. However, please rest assured that your domain name is still valid, even if we aren’t able to display it on our platform. The ENS is still in your wallet, and can be seen on other platforms for sale. We can’t confirm whether it violates the Terms of Service of other websites. 
 
I know that this is not the response you are expecting to hear, and I understand the disappointment. I wish I can provide you with a better resolution, so if I can help you in another way, please let me know. Don't hesitate to reach out back to me, I'm just here for you.

[Pitter108]

What's that mean ☝. Is that means we lost our money ? How can I sale my nft ?
Any response I really appreciate

[sanskaryo]

I think if OS continues to delist domains like this then ens should also update its list of valid domains and remove those which do not fulfill the terms and conditions of exchanges or just show a warning sign at the time of minting

[sanskaryo]

https://adraffy.github.io/ens-normalize.js/test/resolver.html#%E3%83%AA%E3%83%B4%E3%82%A1%E3%82%A4%E3%83%BB%E3%82%A2%E3%83%83%E3%82%AB%E3%83%BC%E3%83%9E%E3%83%B3 リヴァイ・アッカーマン is showing normalized but still not appering on OS , is there any other way to check normalization before minting a domain

[toemm]

This is another answer from opensea customer service

Hello,

Thank you for patiently waiting for our response. How are you doing? I hope you are well.

I am very sorry to hear that your ENS domains doesn't show in OpenSea. I understand that this has been frustrating, and I do apologize for the inconvenience it has caused. Rest assured that I will do my best to clarify why your ENS name isn’t visible on OpenSea.

Taking a look at the item’s history, your ENS name was delisted under our Terms of Service, meaning it will no longer appear on our platform. I understand this can be really disappointing.

If an ENS name violates our Terms of Service, or we receive a DMCA request, we may be obligated to remove it from OpenSea. However, please rest assured that your domain name is still valid, even if we aren’t able to display it on our platform. The ENS is still in your wallet, and can be seen on other platforms for sale. We can’t confirm whether it violates the Terms of Service of other websites.    I know that this is not the response you are expecting to hear, and I understand the disappointment. I wish I can provide you with a better resolution, so if I can help you in another way, please let me know. Don't hesitate to reach out back to me, I'm just here for you.

Can a dev confirm that this is true? Meaning with the update OS doesn't list the domain anymore?

[pho4]

https://adraffy.github.io/ens-normalize.js/test/resolver.html#%E3%83%AA%E3%83%B4%E3%82%A1%E3%82%A4%E3%83%BB%E3%82%A2%E3%83%83%E3%82%AB%E3%83%BC%E3%83%9E%E3%83%B3 リヴァイ・アッカーマン is showing normalized but still not appering on OS , is there any other way to check normalization before minting a domain

based on what i've read so far around on discord and on gitbub, the character "ー" got caught up in one of the latest updates which renders all names with that character as 'invalid'. hopefully the ens team is willing to look at that character specifically since it bricks a chunk of japanese characters.

[delbagir]

it seems that even on my metamask, under the ENS assets, i dont see the ens domain i registered. can we have an update on this?

[SkuIlz]

I bought 3 digit domain, using non character. When I check the domain it says valid and registered by me. But its delisted in opensea and it says invalid address with red background

[SkuIlz]

[yoleyo]

and we all waiting for a fix, but nothin seems to be coming

[serenae-fansubs]

It is coming! I assure you, devs have been hard at work on this: https://discuss.ens.domains/t/ens-name-normalization/8652/128

Not all names will become valid after the change though! The code is not final, but this live demo site can be used to get a good idea of what will be valid/invalid per the metadata: https://adraffy.github.io/ens-normalize.js/test/resolver.html

[SkuIlz]

It is coming! I assure you, devs have been hard at work on this: https://discuss.ens.domains/t/ens-name-normalization/8652/128

Not all names will become valid after the change though! The code is not final, but this live demo site can be used to get a good idea of what will be valid/invalid per the metadata: https://adraffy.github.io/ens-normalize.js/test/resolver.html

Hello thank you for reply , i checked live link you sent, I entered my domain which had delisted from opensea “aрe.eth” the “р” alphabet is different thats why they delisted it from OS. Do you think they will fix it ?

[SkuIlz]

[Shark43]

hi, i bought some JP ENS:
ユクシー.eth
0x17595d4ed4e2d0af4ce013560fa2884f8efa38234cd0622fec0645c7e891a257
https://metadata.ens.domains/mainnet/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/19921806114804879714177476371129274652135542314822121026147215006123759778213
マーシャドー.eth
0xaa2dc94305a7a5677166c8564f95e269270dfcc1484b6f2925f889f3662157df
https://metadata.ens.domains/mainnet/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/70014084200189111013728177536713399682074110973574252266516382054367630835630

i think the problem is with this character 'ー' that is used in most of JP words. hope you can fix this character

with https://adraffy.github.io/ens-normalize.js/test/resolver.html#%E3%83%A6%E3%82%AF%E3%82%B7%E3%83%BC say it normalized but with the main api not

[Swavevince]

any progress? still waiting on my n°1.eth , n°2.eth, n°3eth,.. n°5eth, n°7eth n°9eth n°10.eth n°20.eth and n°50.eth??

⚠️ Disallowed character "{B0}" any news on when it will get fixed?

[coltron-code]

@mdtanrikulu Is there a status update on this issue?

I notice we're still receiving support tickets and forum inquires about this.

[mdtanrikulu]

@mdtanrikulu Is there a status update on this issue?

I notice we're still receiving support tickets and forum inquires about this.

Hi @coltron-code and everyone wondering the progress in here.

We patched ens-app as in same fashion as metadata service to prevent future delisting issues. Currently both services work with ens-validation library, which means no other name registered trough ens-app will be delisted from now on.
Of course this is not an ultimate solution, since the problem is in core of ens-validation library itself, but a measure to keep the issue under control in some extent.

The main work and discussion regarding normalization continues here.

When the normalization spec settles, we will be using this standard in all services asap.