ENS name: curion.eth
My reasons for wanting to be a delegate: One’s online identity will be increasingly important from now on, and I want to actively assist in this tool of identity being a powerful and equitable tool. No blockchain identity is as widely usable and recognized as that on Ethereum in my opinion, so I’d like to participate in the development of its identity system.
My view on each section of the proposed ENS Constitution
-
Name ownership is an absolute right: Agree, if one can afford it. While being considered a public utility, I view the ENS as an entity that provides a service, but one that is thankfully less profit-focused because of the public good that can be done through a widely-accessible name system. In line with this mission, to stay viable and provide optimal utility, costs may have to change, and any increase in cost will likely be transparent and justifiable toward the mission of the ENS.
-
Registration fees exist as an incentive mechanism: Agree. A modest registration fee acts to decrease spam registrations and provide the ENS DAO with enough funding to maintain and improve the entity it governs. Based on the quality and activity of the names in the namespace, I support adjusting pricing to prioritize quality and minimize speculative purchasing. I also support adjusting pricing to make sure the ENS remains reliable and usable.
-
Income funds ENS and other public goods: Agree. Income may be distributed on a scale ranging from being most directly related to current ENS development to more far-reaching or less-directly-related projects based on how much income is coming in.
-
ENS Integrates with the global namespace: Agree. I think the example from the proposed Constitution sums up my thoughts perfectly: “ENS governance should grant control of a top-level domain to its owner in the DNS system on request.”
My web3 qualifications / skills: I have beginner experience with web3 app and ERC20/ERC721 token development using python, javascript, and solidity, attained from duplicating and modifying tutorial-based projects. I have 7+ years of experience coding in general that I am beginning to apply to web3.