ENS name: serenae.eth

My reasons for wanting to be a delegate: My primary hobby is translating anime and creating fansubs for the community. Over the years, I’ve seen many cases where subs get lost because of some centralized website or tracker went down. I got introduced to ENS and IPFS and went down the rabbit hole, and am excited about how this can help the community. Admittedly it’s just a small slice (anime fansubbing), but the principles are the same for other types of content creation. I just want to do my part to help make ENS a success.

My view on each section of the proposed ENS Constitution:

• Name ownership is an absolute right: Strongly agree. This is the core of what makes ENS important.

• Registration fees exist as an incentive mechanism: Agree. You can easily register out 10, 50, 100 years in one transaction if you wish. The fees and expiry process help ensure that ENS names actually get used rather than merely squatted on or lost forever / burned.

• Income funds ENS and other public goods: Agree, though admittedly this article is quite open to interpretation as to what constitutes a “web3 public good” or what “conflicts with the goals of ENS”.

• ENS Integrates with the global namespace: Strongly agree. Interoperability will be a must, and doing so in a way that doesn’t sacrifice decentralization or Article I is an absolute must.

My web3 qualifications / skills: My main skills at the moment on the web3 side are around IPFS and the creation of decentralized and uncensorable websites using ENS as the anchor/entrypoint. Excited to see the integration of monetary incentive protocols on top of IPFS to ensure that people aren’t completely dependent on pinning services, etc. Other than that, I am a backend developer in the real world, with lots of experience on low-level protocols like TLS, DNS, etc., so I want to bring my skills and meld them into the metaverse and web3 virtual plaza.