This is, let’s say a campaign promise of mine
There are some changes I would like to propose on the constitution. Before making individual proposals for amendments, I would like to make a temp check on the overall reaction to them.
The primary purpose of registration fees is as an incentive mechanism to prevent the namespace becoming overwhelmed with speculatively registered names.
A secondary purpose is to provide enough revenue to the DAO to fund ongoing development and improvement of ENS. The goal of the any registration mechanics should be to allow names to be, in this order, useful, available and affordable. ENS governance will not enact any fee other than for these purposes.
I would like to remove the striked out version. I believe that the mandate of the DAO to provide for ongoing development for ENS is already covered in article III. My fear here is that it could enable a rent-seeking governance in the future, in which the expanding governance needs to raise fees to cover the cost of the expanding governance. In a sense, article II limiting fees works as a sort of ceiling for the DAO’s power to enact rent on buyers.
The second sentence (notice I replace the word registration fee, with registration “mechanics”) added creates a more specific goal which is to make sure that names are useful (most names are being used by people who are using it), available (ie, most are not held by speculators and a new users can still find useful ones to buy), and in last affordable (which is subjective and only a third priority after the last two).
IV. ENS Integrates with the global
In order to facilitate making the most widely usable naming system, ENS aims to integrate with the legacy DNS naming system to the greatest extent possible without sacrificing decentralization of ENS. ENS will aim to create new features to improve the overall experience of internet users and be compatible with other naming systems as long as they are not in conflict with ENS or DNS. ENS governance will not enact changes that compromise ENS’s ability to do this.
The goal here is to emphasize that ENS is not subject to DNS or Ethereum, but rather aims to be a protocol for everyone. It also creates a framework that allows ENS to be compatible with other naming systems and other blockchains, but within a very limited framing: that the naming system is compatible with ENS and DNS for now and the foreseeable future.
Example: let’s say that there exists another naming system in another blockchain. Let’s say it uses the TLD .foo. We could consider granting them .foo in ENS if:
- .foo has some special reserved status in ICANN and it’s deemed unlikely that it a new DNS .foo would be launched.
- Foo Naming System respects .eth names and does a best effort to resolve .eth names to a recent snapshot of .eth
- .foo in ENS would similarly use some mechanics to resolve names to a recent snapshot of theirs (similar how L2 subdomains would work, or how other TLDs work)
While some might find this weird, and would love to bet on a sort of ENS maximalist position in which ENS eventually takes over DNS and everything else dies, I actually think this framework would be a positive sum for everyone. It would provide an incentive for other naming systems to be ENS compatible and would allow ENS names to be resolved to their proper owners in other blockchains.
While I believe in Ethereum and will always hold it dear to my heart, I also believe in peaceful existence with other blockchains and naming systems, and we would all benefit if we all worked together to allow cross compatibility. In fact, if ENS names were respected in other blockchains, this would be better, not worst for ENS owners. And finally, the strict requirements filters out naming systems that don’t actually care for proper decentralization and aim to sell names that belong to DNS or other naming systems.
I would love to see a future in which a bitcoin wallet can use ENS names to make their experience better, in which an Avalanche user could bridge ether to avax using names that exist in both blockchains at the same time.
ENS is not just a naming system for ethereum. It’s an identity system for everywhere.
- Support changes to Article II
- Against changes to Article II
- Support changes to Article IV
- Against changes to Article IV