> For the complete documentation index, see [llms.txt](https://docs.convexfinance.com/convexfinance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convexfinance.com/convexfinance/general-information/governance-and-voting.md).

# Governance and Voting

Convex governance has moved to a dedicated on-chain voting platform for **vlCVX** holders.

The new system lets **vlCVX** holders and their delegates vote through Convex on DAO proposals and gauge weight allocations across supported protocols. Convex aggregates **vlCVX** voting results and uses those results to submit Convex's vote through the relevant external governance contracts.

Use the new Convex Governance UI here:

<https://www.convexfinance.com/vote>

### What changed

Previously, many Convex voting flows were handled through Snapshot. The new voting system introduces on-chain Convex voting contracts for:

* **DAO proposal voting** — votes for supported protocol governance proposals.
* **Gauge weight voting** — weight allocation across supported gauges.
* **Separate delegation** — users may delegate DAO voting weight and gauge voting weight independently.
* **A dedicated governance UI** — active proposals, vote weight management.

### Supported voting categories

The Governance UI currently organizes voting into these categories:

* **Curve Gauge Weights**
* **f(x) Protocol Gauge Weights**
* **Curve DAO Proposals**
* **f(x) Protocol DAO Proposals**
* **Frax DAO Proposals**
* **Resupply DAO Proposals**
* **Convex DAO Proposals**

If there is no active proposal for a category, the UI will show that no proposal is currently available.

### Who can vote

Voting power comes from **vlCVX**, which is created by locking **CVX**.

A wallet can vote if it has effective **vlCVX** voting weight for the relevant voting epoch. Effective voting weight may come from:

* the wallet's own locked **CVX** balance, or
* voting weight delegated to that wallet by other **vlCVX** holders.

To lock **CVX**, use the Convex lock page:

{% embed url="<https://www.convexfinance.com/lock>" %}

### Voting epochs and timing

**vlCVX** voting power is epoch-based. Convex lock epochs begin weekly on **Thursday at 00:00 UTC**.

For voting, the proposal records an epoch when the proposal is created. Your voting weight for that proposal is based on your **vlCVX** balance and delegation state for that recorded epoch.

Important timing rules:

* **CVX** locked during the current epoch counts after the next epoch begins.
* Delegation changes take effect from the next epoch.
* Relocking expired **CVX** can restore voting power for the current epoch.
* If a lock has expired, the user may need to process expired locks or relock before voting.

### DAO voting

DAO proposals are yes/no votes. A voter may allocate voting weight between yes and no using percentages.

Examples:

* 100% yes / 0% no
* 0% yes / 100% no
* 60% yes / 40% no

Convex aggregates **vlCVX** votes and uses the final percentage result when submitting its external governance vote.

### Gauge weight voting

Gauge weight proposals let **vlCVX** holders decide how Convex voting power is allocated across gauges for supported protocols such as Curve and f(x) Protocol.

Voters allocate 100% of their vote weight across one or more eligible gauges. Convex aggregates all votes and submits the final gauge weights through the relevant external gauge-voting system.

### Delegation

Delegation lets another address vote with your **vlCVX** weight without moving your **CVX** or **vlCVX**.

The new Governance UI supports separate delegation flows for:

* **Gauge weight votes delegate**
* **DAO votes delegate**

You can delegate to a specific address or use the UI option to delegate to the Convex team.