Name (organization or individual)
Camelot DAO (organization)
Wallet Address or ENS
0x2e3BEf6830Ae84bb4225D318F9f61B6b88C147bF
Tally Profile URL
What area are you most interested in contributing to? choose up to two tags
- DeFi development on Arbitrum
- Improving Governance participation
Please share your stance on overall goals for the DAO
We believe that the Arbitrum DAO should primarily focus on two areas:
- Supporting the development of new and needed applications
- Helping onboard new users who would benefit from the applications on Arbitrum
As the native DEX and launchpad for new projects on Arbitrum, Camelot is uniquely positioned to help with both of these areas. Our Round Table Protocols represent the majority of applications on Arbitrum and together, they help make Arbitrum and Camelot a collaborative and supportive home for innovation.
Sample Voting Issue 1
- Against
- Such large DAO token allocations should generally only be made for programs which are overwhelmingly popular. The mere fact that the vote is nearly 50/50 should show that it probably shouldn’t pass. To make the vote less contentious, we would probably recommend reducing the payment schedule to monthly or quarterly instead of annually (making the DAOs upfront commitment smaller by an order of magnitude). We might even recommend introducing a trial period which is only continued if the trial hits certain performance metrics.
- DAOs should always try to maximize the accountability of individuals and entities that interact with them. Paying for services on a performance basis should almost always be preferred, and DAOs should try to structure compensation plans that align incentives. Especially in decentralized environments involving anonymous individuals, economic incentives must be aligned to ensure quality outcomes.
Sample Voting Issue 2
The first vote should have triggered a trustless execution of the hack repayment. It’s unclear what to do after two such votes when neither had executable code tied to their outcomes. Thus, we would never put such a monumental vote to governance without the executable code attached.
The reimbursement amount should be determined by the token holders as they have the long term interest of the project in mind. If executable code had been attached to the first vote, they would have fully reimbursed the hack victims. If token holders directly voted for this code to be executed, it would have been the right outcome.
Languages I speak and write
English, French