Camelot Delegate Communication Thread

[Camelot]

June 2025 voting

---

---

Snapshot votings

Adjust the Voting Power of the Arbitrum Community Pool & Ratify the Agentic Governance Pivot

Vote: B - Reduce delegation to 100K

@Camelot

Camelot supports Option B to reduce the delegation to 100,000 ARB.
At the time of the original proposal, Camelot voted against the initiative since we believed it was not bringing any meaningful value to the DAO. The subsequent change in scope from voter enfranchisement to AI-agentic governance provides, in our opinion, one more additional reason to reassess the delegated amount.
However, we recognize the potential value in experimenting with agents in governance, with an amount that is limited to 100,000 ARB delegated versus the initial 7M used by not too many users. AI is increasingly pervasive across various sectors and will likely find relevant use cases in DAO operations and decision-making processes. This represents a legitimate area for controlled experimentation.

Due to this recognition and the fact that only a few months remain for this proposal’s original term, we suggest reducing the delegation to 100,000 ARB and analyzing the results in Q4. This approach allows Event Horizon to continue their agentic governance experimentation while significantly reducing the potential impact on DAO voting outcomes.

Wind Down the MSS + Transfer Payment Responsibilities to the Arbitrum Foundation

Vote: Wind Down the MSS

@Camelot

Camelot supports this proposal to transfer multisig operations to the Arbitrum Foundation and, later if deemed necessary, to OpCo when it becomes operationalized. While there is value in involving the DAO in various functions, multisig management represents the typical task where efficiency and security are the most important features. For this reason, placing these responsibilities in the hands of Arbitrum-aligned entities makes considerable sense: the Foundation’s, having the role of compliance member and having full-time employees that are better trained in OpSec compared to DAO members, and the internal legal capacities, makes them the most suitable interim custodian of these functions.

We also have a general preference for the transactions related to the DAO programs being timely executed. For whoever operated multisigs, is easy to recognize how the current 7/12 or 8/12 threshold is slow and inefficient; but we also can’t realistically go below this threshold in DAO operated multisigs. We realistically see as the only path forward consolidating the functions under Foundation first, and OpCo later.

Reallocate Redeemed USDM Funds to STEP 2 Budget

Vote: For

@Camelot

Camelot supports this proposal as it represents the most logical step forward given the circumstances. The reallocation of redeemed USDM funds to the STEP 2 budget is, in our view, a straightforward administrative action.
We obviously believe these funds should be allocated as soon as possible to avoid losing any interest on the principal.

More importantly, we think this precedent should set a standard for similar cases in which the DAO needs to recover stablecoins and wants to redeploy them quickly. For future instances where external factors force the redemption of approved treasury assets, we shouldn’t be required to go through a snapshot vote for redeployment into previously approved allocations. Such administrative decision should fall directly into the entities managing the treasury of the DAO.

Updating the OpCo Foundation’s Operational Capability

Vote: n/a

Let’s improve our governance forum with three proposals.app feature integrations

Vote: n/a

---

Tally votings

DeFi Renaissance Incentive Program (DRIP)

Vote: For
Confirming the snapshot vote

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

Vote: n/a