I believe they need to be mapped, if we want a good UX.
According to UTS-46 w/ Context O the recommendation for Arabic Numerals is never allow digit mixing. However, that still permits visually identical names for corresponding digits.
According to UAX-15 and visual inspection, 0-3,7-9 are confusable, so either you disallow those characters or pick a preferred one. The recommended solution is to convert to punycode, so the user sees a gibberish name, but now have the information necessary differentiate the confusables characters (if they know the correct punycode form.) For ENS, we don’t have an alternative input form.
- Names should normalize or fail → How do I resolve xyz.eth?
- Names should be valid/accepted/notconfusing or fail/warn. → Is xyz.eth a spoof?
Discussed? yes. Approved? no, that’s the purpose of this discussion!