Camelot Delegate Communication Thread

[Camelot]

July 2025 voting

---

---

Snapshot votings

Audit Committee Technical Expert Elections

Vote: 100% for Gustavo Grieco
While both candidates have good experience, we think Gustavo is a better fit for the role.

Extend AGV Council Term and Align Future Elections with Operational Cadence

Vote: For
We are in support of this proposal. We think the current status of AGV is such that going for a re-election now would be disruptive for the operations. At the same time, we are generally not thrilled by the fact that this situation was forced by basically a 6 months delay in the roadmap of the fund.
That said, we hope that this extension will help the council work in peace and allow the initiative to take off. The goal has always been to create a new line of business for the DAO and we hope that this will come to fruition in the future.

Arbitrum Research and Development Collective V2 - Extension

Vote: Don’t Extend
As others, we think the internalisation of research functions in the AAEs plus the ability for OpCo to engage directly with service providers after the previous vote makes the extension of ARDC not viable. We think the researches were of good quality; that said, the structure falls short in term of actionability post-research. We do see a risk of the gap in not having a research department in the DAO, but our hope is that this gap will be filled by OpCo ability to move more freely.

Entropy Advisors: Exclusively Working with the Arbitrum DAO, Year 2 and Year 3

Vote: For

@Camelot

Camelot is casting the vote in favor on the Entropy Advisors proposal for Years 2 and 3.
We do appreciate the foundational work Entropy Advisors has delivered over the past year. As a key contributor to the Arbitrum ecosystem, we’ve seen how they’ve started the process of professionallization of the DAO’s operations, and we think a prime example is their role in the creation of the OpCo, which promises to streamline execution and reduce governance bottlenecks.

That said, it’s clear this was the inaugural big year for both the Arbitrum DAO and Entropy, and not everything landed perfectly. Initiatives like the GMC/TMC proposal fell short in properly allocating resources to protocols, leading to missed opportunities for ecosystem growth. While we are obviously biased being a protocol, and while we were the only native Arbitrum one getting an allocation, we do aim for an higher tide that lifts all the boats to grow the ecosystem.
The proposal does request an important monetary commitment, totalling $6M plus 15M ARB as bonuses over two years. This is not insignificant, looking at it also in the optic of general treasury management discussion. We don’t view this as a dealbreaker. If Entropy delivers on their commitments, the ROI will far exceed the costs through tangible ecosystem expansion in the form of treasury strategies and better incentives programs.

To us the key point is that this extension positions Entropy just slightly below entities like Offchain Labs and the Arbitrum Foundation in terms of expectations and accountability.
We now have narrower, clearer goals outlined for years 2 and 3 compared to the first year, and for this reason we expect Entropy to step up and produce measurable, tangible value for the DAO. Passing this proposal raises the bar significantly.
As the Arbitrum’s native DEX, we’re particularly keen on seeing Entropy prioritize the utilization of the DAO’s liquid treasury assets within onchain Arbitrum protocols. This means actively demonstrating how the DAO can push for sustainable growth by acting as the “first customer” for builders. We’ve built Camelot to power real yield and liquidity for the ecosystem; we strongly believe Arbitrum is the home of DeFi; we believe Entropy’s efforts here could amplify Camelot’s flywheel and the whole ecosystem growth.

Overall, our expectations are high. We are entrusting Entropy in having a key role in the future of our ecosystem, and we are committed to support them in their work to reach the results we all expect them to achieve.

[Constitutional] AIP: Update the Upgrade Executors

Vote: For
We support upgrading the contracts in a way that is more efficient to call for specific updates, to reduce complexity and potentially also human errors.

[CONSTITUTIONAL] Register $BORING in the Arbitrum generic-custom gateway

Vote: For
We do support every builder that wants to come in Arbitrum so the vote is straightforward. As other delegates, we hope that there will be in future ways to avoid governance votes for this kind of operations which should be easier to execute.

---

Tally votings

[CONSTITUTIONAL] Register the Sky Custom Gateway contracts in the Router

Vote: For
Confirming the snapshot vote, now that the payload is correct

[Constitutional] AIP: Constitutional Quorum Threshold Reduction

Vote: For
Confirming the snapshot vote