It’s complicated, Derek, and it’s an active topic of discussion at the moment. I don’t know how familiar you are with the technology behind ENS but you might want to take a look at these two threads and see if you grasp the issues.
hello everyone.
i’d like to start by saying how excited I am about the future of Ethereum and the ENS project. ENS fills a critical need and is visionary in its melding of the functionality necessary for web3.
however, the project suffers from a huge liability and existential threat: zero-width unicode characters, specifically U+200C(ZWNJ) and U+200D(ZWJ), although there may be more of which i’m unaware.
the utility of these two characters comes from ligature writing systems such as sanskrit …
I’ve got a few remaining questions regarding normalization.
The UTS-46 spec makes a distinction between “registration” and “lookup”, where stricter rules apply during registration. Since ENS is decentralized, aren’t these the same? I feel like the goal here should be have a single procedure that takes user input and makes it standard across all applications and platforms.
One example of this difference is ContextO (Rules #3-#9) . Should ENS name normalization follow ContextO? For refere…
2 Likes