ENS name: awe.eth
My reasons for wanting to be a delegate: I’m passionate about crypto. I’ve been in the space for many years and I want to be on top of the next trends. I’m very bullish on Ethereum being the de facto web3 blockchain and obviously ENS will control the domain infrastructure. I feel like I’m uniquely position because I understand web3 technology more than the average user and have implemented RFC specs on the engineering side. I have a strong background in software engineering.
My view on each section of the proposed ENS Constitution
Name ownership is an absolute right: (Agree/Disagree/Comment)
Disagree. I think we would explore a better name ownership and revenue model that is fair to all parties. I don’t think being a first mover should give you absolute rights.
Registration fees exist as an incentive mechanism: (Agree/Disagree/Comment)
Agree. ENS is a SaaS product and typically reoccurring revenue has been proven to be a successful model for SaaS product. I am opened to exploring additional incentives.
Income funds ENS and other public goods: (Agree/Disagree/Comment).
Agree. Although I could be convinced private entities could be worth pursuing if it’s highly beneficial for ENS.
ENS Integrates with the global namespace: (Agree/Disagree/Comment):
Agree. This would be awesome for everyone involved with this project.
My web3 qualifications / skills:
- Been in Bitcoin scene since 2011. I still have old Bitcoin wallets from 2013.
- Previously a routing and signaling cloud software engineer at Cisco.
- Previously a software engineer at a Bitcoin exchange, Kraken.
- Previously at a crypto hedge fund working in prop trading.
- Currently working on a defi protocol on Ethereum using solidity and other web3 technologies. I understand solidity, familiar with the popular EIPs ad Ethereum’s history, and understand how protocols work across the blockchain.
- I’m very adept with defi products and trading.