Reforming the NCL Framework
I would like to open a discussion on reforming how Cardano approaches the Net Change Limit.
The recent treasury cycle has made something clear to me: the issue is not simply whether individual proposals are good or bad. Many proposals have merit. The deeper issue is that very different types of spending are being forced to compete inside one long NCL window and one largely undifferentiated budget pot.
The NCL is a constitutional treasury guardrail. It caps how far the treasury balance may fall over a defined period and must be agreed by DReps under the Constitution. It is not a protocol parameter; it is a governance safeguard designed to bound treasury withdrawals and force prioritisation.
In my view, the current approach needs reform.
The Current Problem
We are still relatively early in the current NCL window, yet the remaining budget is already under significant pressure.
That suggests the structure may be wrong.
When an NCL window runs for a long period, it creates the appearance of a large available budget. Proposals then naturally arrive early, and DReps are forced to make decisions about a year or more of future treasury capacity before knowing what other proposals, market conditions, ecosystem needs, or strategic priorities may emerge.
The NCL should be treated as a maximum ceiling, not a spending target.
If the limit is raised whenever demand exceeds supply, the NCL risks becoming a formality rather than a fiscal discipline mechanism.
My position is that we should reform the NCL framework before simply expanding future ceilings.
1. Shorter NCL Windows
I think Cardano should move toward shorter NCL windows, likely somewhere between 3 and 6 months, with appropriately sized limits.
Quarterly or half-yearly windows would force DReps to reassess treasury priorities more regularly.
Market conditions change. ADA price conditions change. Proposal quality changes. Ecosystem needs change. Governance priorities change.
A shorter cadence would make treasury governance more responsive and reduce the risk of over-allocating too much spending capacity too early in a long window.
This does not mean Cardano should spend less forever.
It means we should decide more frequently, with better context.
2. Bucketised Budgets
Before setting or raising an NCL, DReps should debate and agree broad category-level budget buckets.
For example:
- Core infrastructure
- Wallets, custody and security
- Developer tooling
- Governance operations
- Growth and adoption
- Marketing
- DeFi / liquidity / treasury investment
- Reserves and contingency
These buckets do not need to be perfect, but they would force the real conversation:
How much should Cardano spend on each strategic priority?
Right now, every proposal competes against every other proposal. That creates poor comparisons.
A wallet-security proposal should not be judged against the same implicit budget as a commercial adoption proposal.
A DeFi liquidity proposal should not be judged against the same implicit budget as core infrastructure maintenance.
A BTC bridge proposal should not be judged against the same implicit budget as governance operations.
Different categories need different standards:
- Critical infrastructure needs continuity and resilience.
- Growth proposals need adoption targets and ecosystem return.
- DeFi or treasury-investment proposals need risk frameworks, concentration limits, and accountability for losses.
One pot does not capture that.
3. Market-Aware Spending
Cardano also needs to become more market-aware.
In weak ADA markets, every ADA spent has a higher long-term opportunity cost.
That does not mean “spend nothing.”
Critical infrastructure, security, self-custody, developer tooling and essential public goods may still justify spending.
But discretionary growth bets should face a higher bar when ADA is weak.
The NCL should not only ask:
How much ADA can we spend?
It should also ask:
Is this the right market environment to spend this ADA?
4. Build a Sovereign Reserve in Stronger Markets
In future strong ADA markets, Cardano should consider converting a defined, governance-approved portion of treasury ADA into stable reserves and potentially other approved non-ADA reserve assets.
This should be debated carefully and governed transparently.
It should not be ad hoc.
The objective would be simple:
- Spend less ADA when ADA is weak.
- Use reserves to fund essential operations, public goods and strategic opportunities during weaker market conditions.
- Avoid being forced to spend the native asset at the worst point in the cycle.
Longer term, the Cardano Treasury could evolve into something more sophisticated:
- Part operating budget.
- Part sovereign reserve.
- Part ecosystem investment function.
But that requires clear rules.
5. VC-Style Allocation, But Only Within Rules
I am not opposed to the Cardano Treasury eventually acting more like a sovereign wealth fund or VC-style ecosystem allocator.
In fact, I think that may eventually be necessary.
But it should happen inside a properly agreed framework, not through one-off decisions from an undifferentiated NCL pot.
Any treasury investment function should have:
- Risk limits
- Stablecoin and non-ADA asset policy
- Concentration limits
- Conflict controls
- Independent due diligence
- Clear reporting
- Defined return/loss accountability
- Category budget constraints
- A clear governance mandate
The treasury can support growth, DeFi, BTC liquidity, commercial adoption and investment-style proposals.
But those categories should be debated and budgeted in advance.
My Suggested Direction
My current view is:
Reform the NCL framework before expanding the ceiling.
Specifically, I think Cardano should:
- Move toward 3–6 month NCL windows
- Agree category-level budgets before each NCL period
- Build stable reserves in stronger markets
- Use ADA more carefully in weak markets
- Allow treasury investment only within clear bucket, risk and reporting constraints
This would not remove DRep judgement.
It would improve it.
DReps would still decide proposal by proposal, but those decisions would happen inside a clearer treasury strategy rather than inside one large undifferentiated pot.
Questions for DReps
I would welcome views from other DReps and community members:
- Should NCL windows be quarterly, half-yearly, annual, or something else?
- Should DReps agree category-level budgets before each NCL period?
- What categories should exist?
- How much should be reserved for core infrastructure versus growth/adoption?
- Should Cardano build stable reserves in stronger ADA markets?
- Should the treasury eventually act as a sovereign reserve or VC-style ecosystem investment function?
- If so, what risk controls should exist first?
My view is not fixed, but I do believe the current NCL approach needs to mature.
The NCL should remain a real fiscal guardrail, not just a ceiling that gets expanded whenever the proposal pipeline exceeds capacity.