Convex is a governance wrapper with cash-flow hooks

Convex’s core product is simple and aggressive. It aggregates Curve participation so LPs can claim boosted CRV without locking CRV themselves, and it aggregates CRV locking so smaller holders can access veCRV-style economics without taking a four-year illiquidity bet.

The token design follows from that product stance. Convex manufactures two things at scale: (1) a “communal” veCRV position and (2) a voting facade over that position. In practice, the protocol asks users to accept a trade. You give up direct control over veCRV and get convenience, pooled boost, and a derivative stack you can trade around.

That derivative stack matters because it partitions the system into roles:

cvxCRV is the key derivative for CRV stakers. When a user deposits CRV, Convex locks it “forever” as veCRV and returns cvxCRV 1:1. Convex’s own guides underline that this conversion is irreversible via the platform.

CVX is the meta token. It is staked for a share of platform fees (paid as cvxCRV), and it is used for voting on proposals like gauge weights and protocol changes.

vlCVX is the governance activation layer. To vote, CVX must be locked for a minimum of 16 weeks in epoch-based locks. Convex then uses vlCVX outcomes to steer how it votes with the ve-assets it controls across integrations (Curve and others), with explicit carve-outs where Convex can reserve discretion.

If you are modeling CVX, this is the first constraint. CVX is not “governance” in the abstract. It’s governance filtered through an operator layer that can execute, refuse to execute, or strategically deviate within stated bounds.

If you want a quick refresher on definitions and modeling terms, the tokenomics FAQ covers common questions.

CVX supply mechanics: capped, CRV-linked, cliff-based

CVX issuance is mechanically tied to Curve activity routed through Convex. CVX is minted whenever a user claims CRV on Convex, and minting applies across LP pools and the cvxCRV rewards pool that distribute CRV via the documented minting logic.

The design detail that matters is the decline function. The CVX/CRV mint ratio steps down via “cliffs” as total CVX supply grows, with a new cliff every 100,000 CVX, up to 1,000 cliffs, and a hard max supply of 100,000,000 CVX.

The docs publish the mint logic in code form. In plain terms, CVX minted for a given amount of CRV claimed is multiplied by the fraction of “remaining cliffs” over total cliffs. Early on, it is close to 1 CVX per 1 CRV claimed. As supply approaches the cap, new CVX issuance asymptotically goes to zero.

This is a clean mechanism. It also creates a structural dependence that many CVX holders underweight: the system’s inflation rate is a derivative of Convex’s ability to keep Curve LP flows and CRV claims on-platform. Convex’s token economy is not self-contained. It is parasitic in the technical sense, and that is not an insult. It is the design.

On current completion status, the cap is effectively “in view.” As of March 3, 2026, CoinGecko reports 99,955,334 total CVX supply against a 100,000,000 max supply, and estimates 91,758,226 circulating, based on its supply figures. That matters because once the final cliffs are consumed, CVX stops being an ongoing subsidy and becomes mostly a claim on fee routing and governance leverage.

Allocations: who got what, and how it unlocked

Convex documents a fixed max supply and a fixed allocation framework. The distribution below is presented exactly once, in the required breakdown format.

Two practical implications follow.

First, CVX is not primarily a “governance-only” asset. Half of supply is explicitly aimed at Curve LP rewards, and a quarter at liquidity mining. That is a distribution built for adoption capture, not slow decentralization.

Second, the treasury is explicitly operator-controlled. The treasury wallet is controlled by the Convex multisig, and the docs state that treasury use is “currently” at the discretion of the Convex team. If your valuation assumes governance can restrain treasury policy, the project’s own disclosure should lower your confidence in parameter stability.

Fees and fiscal flows: CRV in, cvxCRV out

The cash-flow story for CVX is real, but it is not “fees go to token.” It is “fees are routed through ve-derivatives, then distributed.” That indirection is core to Convex’s flywheel because it grows the communal ve positions.

For Curve-side activity, Convex documents a 17% total fee on all CRV revenue generated by Curve LPs on Convex in its fee schedule. The published split is:

10% to cvxCRV stakers (paid as CRV), 4.5% to CVX stakers (paid out as cvxCRV), 2% to the treasury (as CRV), and 0.5% to the harvest caller (as CRV).

The second-order detail that matters for modeling is the settlement path for CVX stakers. Fees “paid as cvxCRV” sit as CRV inside the rewards contract until a user claims, at which point Convex locks that CRV as veCRV and mints cvxCRV 1:1 to pay the user. So the fee distribution mechanism is also a CRV lock-and-sink mechanism.

Convex also discloses fee parameter ranges on Curve-side fees. The cvxCRV staker portion can be adjusted between 10% and 15%, the CVX staker portion between 3% and 6%, the treasury portion between 0% and 2%, and the caller portion between 0.1% and 1.0%, with an absolute fee ceiling of 20%.

That is the trade-off in one paragraph. The system can iterate quickly on fee routing, but the token holder’s “take rate” is not immutable. It is bounded. It is still discretionary inside the bounds.

Outside Curve, Convex extends the same architecture to other ve-systems. For Frax Finance, Convex documents a 20% total fee on FXS revenue generated by Frax LPs on Convex, with 10% to cvxFXS LPs, 5% to vlCVX holders (as FXS), and 5% to the treasury. Even if you only care about CVX, this matters because it creates cross-protocol revenue optionality that accrues to certain CVX-holder classes (especially lockers) depending on how integrations are configured.

Governance and control surface: Snapshot + multisig reality

Convex’s governance UI is Snapshot-weighted. Its execution layer is not. The docs are direct that Snapshot is used for voting, and that governance proposals are weighted by vlCVX vote outcomes such that if vlCVX votes 60/40, Convex will submit an on-chain vote 60/40, per its vote execution policy.

But then comes the operator clause. Convex states that the multisig is still required to sign and establish outcomes of all CVX Snapshot votes, and that proposals viewed as “blatant attacks” damaging Convex or Curve will not be signed for. That is a discretionary veto. It may be defensible. It is still a veto.

The voting schedule and thresholds are also published. Gauge votes are bi-weekly, and gauge weight votes have no quorum. Curve ownership governance votes and Curve parameter governance votes each have a 15% quorum. A gauge must receive at least 0.05% of votes before weight is assigned.

To obtain that voting power, CVX must be locked. The lock minimum is 16 weeks, locks are bucketed into weekly epochs, and tokens locked mid-epoch are effectively locked for 16 weeks plus the remaining time until the next epoch boundary. There is also a “kick” mechanic for expired locks left idle. CVX that sits idle longer than 4 epochs can be kicked, with a bounty of 0.25% per epoch past the grace period paid to the kicker.

Now to the part that should drive any serious risk-weighting: the documented admin surface.

Convex discloses a 3-of-5 multisig and names its members, including two associated with Convex Finance and three associated with other DeFi entities (Llama Airforce, Votium, Frax Finance). The same page lists admin rights that include updating core system components like the stash factory and pool manager, controlling the arbitrator vault, adjusting platform fees within hard-coded ranges, setting the treasury address, setting MasterChef distribution weights, and pausing deposits across the system.

Convex also states “admin controls do not have access to user funds” and therefore “time-lock delays are not required.” From an operator-discretion-skeptic perspective, the key nuance is that “no direct access to deposits” does not equal “no power over outcomes.” Fee routing, reward listings, voting execution, and deposit gating are all economic control points.

Finally, Convex’s integration governance explicitly reserves strategy bandwidth. For Frax gauge-weight votes, Convex may allocate up to 20% of its veFXS weight for “strategic reasons,” with the remainder distributed proportionally to vlCVX votes. Prisma emissions voting has the same explicit 20% strategic allocation carve-out. FX Protocol governance similarly routes votes via vlCVX but allows up to 20% strategic allocation of veFXN.

That is not “decentralized governance” in the strict sense. It is representative governance with explicit operator discretion.

Risk analysis: CVX is exposed to operator discretion more than code

Convex’s docs acknowledge general smart contract risk and emphasize that users are beholden to risks in integrated platforms like Curve and Frax. True. But for CVX tokenomics, the sharper question is where the system’s economic control points sit.

The cleanest summary is this: CVX value accrual is downstream of fee parameters, fee distribution plumbing, voting execution, and treasury usage. Every one of those surfaces is either directly multisig-controlled or multisig-mediated. That does not mean the project is unsafe. It means CVX holders are underwriting governance execution risk.

Top 3 risks

  1. Operator discretion and execution-layer veto (dominant). Trigger: high-stakes votes, contentious gauge allocation, or proposals framed as attacks. Mechanism: Snapshot outcomes require multisig signing to be established, and Convex states it may refuse to sign proposals deemed damaging, plus the multisig can pause deposits and adjust fee routing within bounds. Who bears it: CVX stakers and lockers (through changed fee share, governance credibility loss, and bribe market repricing), and cvxCRV holders (through downstream vote behavior affecting emissions and incentives). Measurable indicators: deviations between Snapshot results and executed on-chain votes, changes to fee parameter values within the published ranges, and use of pause/shutdown powers on deposit contracts.

    This is the dominant risk because it attacks CVX at its point of monetization. CVX is sold as a claim on (1) fee flow and (2) vote-direction influence. Both are mediated. Fee flow is explicitly adjustable in-range by the multisig. The treasury is controlled by the multisig, and its use is currently at the discretion of the Convex team. Voting is filtered through a signing requirement, with an explicit refusal condition.

    Even if you believe every actor is honest, this is still governance centralization risk. It concentrates decision latency and failure modes into a small committee. It also introduces path dependence. In a bribe-driven ecosystem, perceived vote reliability is an asset. If market participants start pricing “Convex might not sign this” into bribe offers, the value of vlCVX vote weight can compress. That compression can cascade. Lower bribe demand can reduce the incentive to lock CVX. Reduced lock participation can make governance easier to capture. Then the multisig becomes even more pivotal, which is circular.

    The trade-off is obvious and sometimes worth it. Convex’s ability to iterate on pool support, reward handling, and fee tuning is partially why it could operate as a high-throughput aggregator. But tokenholders should treat that speed as borrowed decentralization. You are trusting operator policy to remain aligned with CVX’s long-run credibly neutral positioning.

  2. Derivative exit risk and cvxCRV basis instability. Trigger: demand shock for exiting cvxCRV exposure, or market repricing of Curve governance yield versus liquid CRV. Mechanism: CRV deposited to mint cvxCRV is locked as veCRV “forever,” and conversion is one-way on-platform, so exiting depends on secondary market liquidity and pricing. Who bears it: cvxCRV holders primarily, and CVX holders secondarily through fee generation sensitivity to TVL and participation. Measurable indicators: cvxCRV/CRV pool price deviation, shrinking liquidity depth in exit venues, and drops in cvxCRV staking participation relative to outstanding cvxCRV supply.

  3. Emission exhaustion and incentive regime change. Trigger: CVX reaching its max supply and new CVX minting trending to zero. Mechanism: CVX minting is supply-capped at 100,000,000 and declines by cliffs every 100,000 CVX, with minting occurring when CRV is claimed. Who bears it: Curve LPs and Convex LP depositors who historically relied on CVX rewards as part of their total return, plus CVX holders if reduced incentives lead to lower platform usage and thus lower fee generation. Measurable indicators: CoinGecko-reported total supply moving into the final cliffs, declining CVX per CRV-claimed over time, and TVL or deposit share migration to competing lockers or direct Curve participation.

If you are designing around CVX exposure in a broader DeFi portfolio, treat it like a governance-and-fee router with a documented operator layer, not like a fully credibly neutral on-chain institution. For teams doing tokenomics services or token economy design, Convex is still a useful case study in how fee tokenization and vote abstraction create adoption loops, and where the discretion cost shows up in the risk register.

For more write-ups in this format, browse our research reports.



This article is part of our Tokenomics Deep Dive series.