Hi @cp0x and @m0xt, thanks for the detailed pushback. We’re going to answer each concern head-on, because the decision here is simple: either the DAO renews a credible long-term incentive runway as legacy grants end in February 2026, or we knowingly accept increased attrition risk and slower execution at the exact moment CoW is expanding cross-chain and into new flow types.
What are tokenholders “buying” for the next cycle?
We agree with the core premise: incentives should map to an explicit plan. Internally we’re aligned around a focus that can be communicated plainly:
-
Make the core product “boringly reliable” at scale: higher swap reliability, better routing / solver performance, tighter operational loops, and smoother partner onboarding so we can unlock larger, high-volume integrations.
-
Expand addressable flows: support new asset types (RWA, Prediction Market Tokens; etc.) and order types and deepen multi-chain / cross-chain execution so CoW becomes the default settlement layer across ecosystems.
-
Improve value capture durability: prioritise high-quality flow, sustainable fee capture, and better COW token economics, rather than chasing vanity metrics.
It’s the practical work needed to keep CoW ahead in a market where L2s, infra teams, and well-funded competitors recruit aggressively.
Why not adopt something like Lido’s GOOSE + hard KPI gates?
Two separate ideas are being mixed:
-
Publishing clear objectives and updating them periodically, we’re aligned with that. Lido’s GOOSE is a good reference for how to make goals legible and reviewable in public.
-
Turning compensation into KPI-gated cliff events we don’t think that’s the right instrument for this phase of CoW, for one reason: it converts retention into a binary governance risk. The moment you make long-term contributor upside contingent on discrete KPI gates (many of which are materially market-driven), you either (i) set KPIs so soft they don’t constrain anything, or (ii) set them hard and accidentally create an incentive program that top talent discounts heavily (or avoids entirely).
Instead, this proposal already bakes in a strong “checkpoint” mechanism that’s often overlooked:
-
Each 5% streams (the initial one and the one resulting from the buy back) are cancellable/pausable by governance while unvested. Tokens stay under DAO control until streamed.
-
The Committee is subject to annual aggregated transparency reporting.
-
The buyback leg is reported explicitly in treasury reporting.
So the DAO has an always-on “stop button” without turning retention into a coin-flip around a single metric.
Allocation size & benchmarking
Two clarifications:
First: the current draft is not “100M streamed now.”
It’s 50M (5%) streamed over 4 years, plus an authorisation for up to $15M in stablecoins to buy COW over time targeting up to ~50M COW purchased (market-dependent), which will be streamed in the future.
Second: mixing “effective circulating” with “allocation size” leads to the wrong conclusion.
Only the initial streamed portion is issuance from DAO reserves; the buyback portion is non-dilutive by design (it moves tokens from the market into the incentive pool).
So the right lens is: 5% gradual stream with a governance kill-switch + a market-purchase program that directly addresses dilution optics and creates structural buy pressure.
In addition, token incentive design varies wildly, but two grounded reference points:
-
CoW’s own baseline: at TGE, the DAO approved a 15% team allocation managed via the committee model. This CIP is about restoring the runway as that program reaches exhaustion and major grants complete vesting by Feb 2026.
-
Market practice (broadly): employee pools in startups are commonly modeled in mid-single digits to mid-teens and show an average of 24% allocated to the team (the point being: serious projects reserve real upside for builders). pulley.com
What happens to the ~26M uncommitted tokens from the prior pool?
They remain within the Team Grant Allocation framework and should be treated as first-line runway before the DAO meaningfully “taps” the new stream (practically: FIFO usage). The key point is: the new stream is not a blank cheque; it’s a replenishment mechanism that can be slowed/paused if the existing pool plus buybacks are sufficient.
Where does the $15M for buybacks come from, and over what timeframe we’d reach the buyback target?
The buyback authorisation is intentionally “up to” $15M over time, not a single immediate spend.
The current Treasury allocation is nearer to $25M in stables, so the treasury team can either use that reserved assets or inflows from revenue to fund the purchases.
So the correct commitment is:
-
Buybacks must be paced so they do not undermine runway targets, timeframe to be defined with KPK (probably around 1 year)
-
Execution remains under the Core Treasury mandate and must be reported (spent, average price, tokens transferred).
-
If the full 50M target is reached under budget, unspent funds return to the managed treasury (already specified in the draft).
Why we’re firm on the structure
We’re not trying to “win an argument.” We’re protecting the DAO from a very predictable failure mode: grants end → retention weakens → execution slows → partners choose other rails → tokenholders pay the price anyway, just more slowly and with less control.
This proposal is the balanced path because it simultaneously:
-
Restores incentive runway as the old program sunsets in Feb 2026,
-
Cuts immediate issuance vs the rejected “all-streamed” approach,
-
Adds a buyback leg that directly addresses dilution optics and can be paced,
-
Keeps the DAO’s hard power intact (pause/cancel stream; annual reporting).
Process note: given the engagement and the fact that the draft already incorporates the key structural feedback (split stream + buybacks + reporting + safeguards), the intent is to move this to vote on Friday, 9 January 2026, in its current format.