exa256
commented
2 years ago I’m Exa, Technical Cofounder on the Exponent Team and I’d like to apply to be the member of Enzyme Technical Council.
Why I want to be on the Enzyme Technical Council:
I have a shared vision for a DeFi operating system as an integral part of a technology stack. As someone who have developed decentralized applications since 2017, I do not believe a new crypto project should be developing a vault from scratch. I also believe that the Enzyme’s V4 has the most ideal architecture to realize this vision, and Exponent intends to develop products, services and compose DeFi strategies on an application layer in order to reduce development overhead, fasten our speed to market, while ensuring optimal smart contract security for our users.
My involvement as an Enzyme Technical Council member will ensure long term ecosystem value alignment. From that perspective, not only will I provide value in the form of integrator’s product and engineering feedback, but also add value as a representative ecosystem partner in the protocol. Increasing the ecosystem diversity in the form of additional tooling, clients and future smart contract plugins.
My Web3 technical qualifications:
Background:
- 4 years + of experience in Crypto (Crypto Class of 2017), started with Dapp development and Blockchain Network Infrastructure
- Software Product and Engineering, both as individual contributor and as a manager
Relevant Technical Skills:
- lead an agile software team to design, develop and ship DeFi applications from end to end.
- knowledge in web3: smart contract development, dApp tooling via Hardhat and EthersJS
- ability to help debug mainnet transactions through the use of tenderly or ethtx, can understand and decode ABI-encoded inputs.
- Gnosis Multisig interactions on a daily basis, knowledge of standard key management opsec as part of a DAO organization.
- know how to set up alerts and notification systems for Gnosis multisig and Vault contract interaction through Tenderly and Discord notification bots.
- led interaction with an external team of auditors through extensive code audits
My recent experience and involvement with Enzyme:
- I have worked together alongside Enzyme’s engineering team since Enzyme V3 to build and ship the Exponent Beta application to Ethereum mainnet.
- walked through and familiarized myself with Enzyme documentation and codebase at multiple level of integration:
- smart contract: being one of the first to interact with Enzyme’s contracts from Solidity
- backend service: custom rebalancer and trade service that submits batched transactions on Enzyme vault via Enzyme TypeScript SDK
- frontend interaction: oversee and help lead technical direction for one of the first custom client-side applications that consumes Enzyme’s event logs and data API.
- Provide Enzyme’s team with technical feedback from the integration perspective
- Recently a speaker at E2 Summit
You can find me on:
Ethereum: exa256.eth Email: exa@exponent.ai GitHub: https://github.com/exa256
or on Exponent Discord: https://discord.gg/43jv3UKUeK
teawaterwire
ChainSecurityAudits
ENZIP: 11 Title: Growing the Enzyme Council and working towards Governance 2.0 Author: Mona El Isa, Avantgarde Status: Draft - discussed in council meetings, iterated and officially voted on snapshot Type: ENZIP Created: Feb 22nd, 2021
Background In February 2019, Enzyme Council came into play as the first DeFi protocol to decentralise its governance. We structured the Council as a technically skilled and user representative group of people and granted the decision making authority of the following actions to the Council:
We’ve managed to maintain a stable governance process throughout. However, with the recent growth of the protocol and the roadmap ahead, the workload is only increasing and having one council to do all tasks isn’t the most optimal way forward.
This proposal served to explore the possible future direction of the council as well as a call to action to encourage new applicants to get in touch!
Governance 2.0: Expanding into squads and adding new members
The council is currently made up of technical and experienced users but they all have different skill sets. The idea of breaking up the protocol into squads should enable higher efficiency and throughput for what the council (and protocol) can deliver.
As the protocol grows in complexity and we start to imagine multiple deployments on different chains, it is likely that the workload of the technical council is going to grow exponentially and thus the governance required with it. As a result of this, we proposed splitting the council into squads which focus on different aspects of the protocol.
Squad 1: Protocol Changes, Upgrades and Emergency Operations: Ideally made up 100% of technically skilled web3 developers or auditors who have experience with the Enzyme Protocol.
Squad 2 : Strategy, Fees & Tokenomics: A team made up of technical experts who are very familiar with Enzyme and can help increase use-cases around MLN. Eg. Staking, gated communities, L1/L2 strategy, gameFi etc.
Squad 3: Grants, Ecosystem, Operations, Treasury & Accounting: Taking care of payments, accounting and making sure that treasury is managed efficiently. Made up 50:50 of investors with grant/ecosystem growth experience and user representatives who can work towards growing the protocol grants and strategically incentivizing the work that needs to be done.
The other change that we proposed involve reducing the quorum on squad 1 from 50% to a fixed 4 votes (irrespective of council size). As we grow, this will help the council to be able to react quickly to protocol changes or emergencies when required.
This isn’t a plan we need to implement overnight, but something that we plan to work towards in phases.
As a starting point, we will separate the Technical Council role and keeping the voting threshold at 50% for a council < 10 people and 40% for a council > 10 ppl. This involves growing the technical council.
Growing the Technical Council We’d like to invite anyone who feels they have the skill sets laid out below to apply to join the Enzyme Council.
Minimum requirements:
Additional nice to haves:
How do I apply? Please respond below with the following information:
ETH Address: ENS name: (Optional but preferred)
Why I want to be on the Enzyme Technical Council: (Your statement of intent)
My Web3 technical qualifications: (Projects you’ve contributed to, DAOs you are a member of, previous delegate experience, etc.)
My recent experience and involvement with Enzyme: (Code or audit contributions, social media engagement, usage of contracts, etc)
Additional links: GitHub: Additional relevant experience with Enzyme: Other relevant information:
What do I need to know? Known identities Need to disclose any conflicts up front Fiduciary duty Remunerated role
Application process will remain open until February 8th, 2022.