ENS name: angelfish.eth
My reasons for wanting to be a delegate:
If ENS is to achieve universal adoption, it must be magnitudes cheaper to register a name and use (e.g. to set your reverse record).
To facilitate a fast and safe transition of ENS to Layer 2 and other scaling solutions, ENS DAO needs a delegate that is deeply knowledgeable about not only the mechanics but also the security and decentralization guarantees of the myriad of different scaling and bridge solutions. And secondly, a delegate that possesses the writing skills to clearly communicate the risks and progress of the scaling effort.
My capacity to do both is demonstrated through my role as Product and Ecosystem Lead at Matter Labs, the team building the first EVM-Compatible ZK Rollup: zkSync, and my skills can be verified in the section below.
As projects that seek to extend the Ethereum ethos of fairness, inclusion, and resilience, ENS and Matter Labs share substantial value alignment in our commitment to open source and community ownership.
Fun: a picture of me showing ENS developer Makoto my ENS names! https://twitter.com/makoto_inoue/status/1419307573627527174?s=21
My view on each section of the proposed ENS Constitution
- Name ownership shall not be infringed: agree
- Fees are primarily an incentive mechanism: agree
- Income funds ENS and other public goods: agree
- ENS Integrates with the global namespace: agree
My web3 qualifications / skills:
- For my technical background and writing skills, check out the last 9 articles written on zkSync’s Medium Blog
- My tweet thread on the security properties of popular Ethereum bridge solutions: https://twitter.com/0xangelfish/status/1454119079975919626?s=20
- previous experiences:
- president of Blockchain @ UCLA, an active governance delegate for Uniswap, Compound, Aave, and more
- software engineer at MetaMask
- implemented Autonomous Proposals for Aave governance
- deployed a Yearn Vault Strategy