Opening here for discussion to choose an ENS name we can dedicate to documentation purposes.
I didn’t want to mention it in the ENSIP proper, but the specific thing we are trying to avoid is using “example.eth” in our documentation because somebody actually controls that. In the web world, example.com is reserved. Many people have used “MyDomain.com” and “YourServer.com” for examples, which of course for SEO reasons resulted in somebody setting up a domain there for web hosting and they got an immediate unearned rankings boost.
|Author||William Entriken <firstname.lastname@example.org>|
This ENSIP defines a specific ENS name, ###INSERTNAMEHERE###.eth to be used for demonstration purposes…
When writing documentation, it is helpful to refer to a concrete name of something to inspire thoughts about how that thing might work.
For example, with HTTPS websites hosted on legacy DNS we can refer specifically to https://example.com.
Further motivation is discussed in the comparable RFC 2606 and RFC 6761. One important reason is that propogating documentation for a specific name, when that name is controlled by an individual party, gives that party a strong motivation to make malicious use of that name.
This specification standardizes one ENS name we can use for similar purposes.
The name ###INSERTNAMEHERE###.eth shall be reserved for this purpose.
It is currently locked and nobody is able to make any use of this name. Therefore everybody is free to refer to this name.
A client website or other tool using ENS MAY warn or error before allowing interaction with ###INSERTNAMEHERE###.eth as this can be a known undesirible action.
A documentation page may say:
You can input your own ENS name such as ###INSERTNAMEHERE###.eth into the box.
Copyright and related rights waived via CC0.