[Draft] Approval of ENS Name Normalization Standard

[raffy]

[Draft] Approval of ENS Name Normalization Standard

Status	Draft
Proposal	ENSIP-15: ENS Name Normalization Standard
Author	raffy.eth

Abstract

Since Normalization isn’t enforced on-chain, there is no code for the DAO to execute. Instead, approval for ENSIP-15 should be confirmed through social vote.

Objectives

• Replace ENSIP-1 § Name Syntax “UTS-46 algorithm” with this ENSIP-15.

• Agree to use ENSIP-15 for a safer end-user experience:

  • 

  • 

  • 

• Although not critical to Normalization, I recommend that names visible to the user should be beautified for a more consistent appearance across devices. High-priority use-cases: ENS Metadata Service and etherscan.io primary names.

  • For example, these are the same emojis:

---

This is my first post in here. I’m not sure on the procedure or format.

[zadok7]

Just wanted to say @raffy you’ve done amazing work on Normalization

[serenae]

This looks great to me. Technically the new app is already using this too!

Does a new ENSIP need a Snapshot vote? I see other newer ENSIPs too, but I don’t think we’ve ever voted on them explicitly, as they don’t affect the core ENS protocol.

ENS Improvement Proposals

[nick.eth]

@serenae

Does a new ENSIP need a Snapshot vote? I see other newer ENSIPs too, but I don’t think we’ve ever voted on them explicitly, as they don’t affect the core ENS protocol.

ENS Improvement Proposals - ENS Documentation

In general no. Given this is a significant change in how ENS names resolve, which affects existing names, I don’t think there’s any harm in getting formal DAO approval for it.