[Convex] Authorize Future Activation of Convex On-Chain Voting

Summary

• Authorize Convex to turn on on-chain voting once the voting contracts have been deployed and the UI has been updated.
• Confirm community support for moving Convex governance toward the on-chain voting system described in the convex-eth/voting repository.

Abstract

Convex has developed on-chain voting infrastructure for vlCVX holders and delegates, described in the convex-eth/voting repository. The system is intended to support on-chain DAO voting and gauge voting across supported protocols.

This proposal asks vlCVX voters to authorize the future activation of that system once the required contracts are deployed and the Convex voting UI has been updated to support it.

Passing this proposal should be understood as approval to turn on Convex on-chain voting at a later date, after the technical prerequisites are complete. It should not be understood as an instruction to immediately activate the system, nor as a separate authorization for deployment or testing work.

Motivation

Convex governance currently relies on Snapshot voting to collect vlCVX holder preferences. Snapshot has been effective, gasless, and accessible, but an on-chain voting system provides a path toward a more transparent and verifiable governance process.

Once deployed and supported by the UI, on-chain voting will allow Convex to move governance participation and vote aggregation closer to the protocol layer. This is a natural progression for Convex as its governance role spans Curve, F(x), Frax, Resupply, and Convex-specific decisions.

The purpose of this proposal is to avoid ambiguity once the contracts and UI are ready. Rather than requiring a separate governance vote at the exact point of activation, this proposal gives advance authorization for Convex to turn on the on-chain voting system after the required deployment and interface work has been completed.

Specification

If this proposal passes, Convex is authorized to activate on-chain voting in the future once the following conditions have been met:

1. The relevant on-chain voting contracts from the convex-eth/voting repository have been deployed.
2. The deployed contracts have been configured for the intended Convex voting flows.
3. The Convex voting UI has been updated so vlCVX holders and delegates can interact with the on-chain voting system.
4. The team has completed the required readiness checks for production use.

Once these prerequisites are complete, Convex may turn on the on-chain voting system for future governance activity without requiring an additional Snapshot proposal solely for activation.

This proposal does not:

• Activate on-chain voting immediately.
• Replace Snapshot voting before the contracts and UI are ready.
• Authorize or define a new contract deployment process.
• Change CVX tokenomics, vlCVX lock mechanics, emissions schedules, user balances, or existing voting weights.
• Migrate any already-active Snapshot vote into the on-chain system.

Voting Options

For: Authorize Convex to turn on on-chain voting in the future once the contracts are deployed, configured, and the UI is updated.

Against: Do not authorize future activation of on-chain voting at this time.