Registered Emoji contains "EF%B8%8F" symbols


I register the emojis below with bulk registration tools from on Jul-21-2022; and the emojis are copied from The Transactions (Txn) are as below:

:broom:.eth, :toolbox:.eth, :magnet:.eth

:mahjong::mahjong::mahjong:.eth, :coffee::coffee::coffee:.eth, :watch::watch::watch:.eth, :snowflake::snowflake::snowflake:.eth,:hourglass::hourglass::hourglass:.eth, :frowning::frowning::frowning:.eth, :keyboard::keyboard::keyboard:.eth, :arrow_up::arrow_up::arrow_up:.eth, :writing_hand::writing_hand::writing_hand:.eth, :airplane::airplane::airplane:.eth

To my great surprises, these Emoji domain are shown " invalid names" when I review them later.
In fact, each emoji appears to have “EF%B8%8F” symbol with it on registeration page, for example: :snowflake::snowflake::snowflake: looks like ":snowflake:%EF%B8%8F​:snowflake:%EF%B8%8F​:snowflake:%EF%B8%8F "

I opened ticket in ENSDAO discord and had an discussion with Cthulu.eth and learned that invalid names will be refunded if they are still remain invalid after the new normalization releases.

My requested will be

  • can you check whether these emojis will be valid or not under the new normalization
  • will the refund still be effective if some names got expired by the time of new normalization release.
  • how can i get refund ASAP if I choose to give up those names that will still be invalid under new normalization
  • can ENSDAO give necessary guidance and notice to general public [including third parties] on what is supported and what is not

Look forward to your action.


@nick.eth can you please take a lookk at this issue?

That is because the tool you used to register those names did not properly strip out the FE0F character. That’s the “%EF%B8%8F” you see, basically a special control character used for display purposes.

That FE0F character is stripped out during normalization. So ❄️❄️❄️ gets replaced with ❄❄❄, and that’s the name that the ETH address is resolved from.

❄️❄️❄️.eth is still “valid” in the sense that you can still use it in client wallets/sites. It’s just that ❄️❄️❄️.eth and ❄❄❄.eth will both point to the address that ❄❄❄.eth resolves to (so not your address).

That is all true today and in the upcoming normalization changes. Nothing has changed with regards to that FE0F character, it was stripped out before, and will continue to be stripped out.

Those are not names that are allowed today or were ever allowed in the past. After the new normalization changes are in place, I think there may be refunds for names that used to be allowed in the official ENS manager app/site. But in your case, since you used some unofficial and unsupported third-party tool, I don’t know whether any refund would apply to you.


thanks serenae for your reply.
I consider it being a lessons learned. apprecited

it’s not a lesson learnt, they basically mean “use only our frontend to register emojis and you cannot even refer to unicode, only our frontend”, kinda bottlenecking the whole decentralised thing if you ask me