Eastern Cardano Council - Net Change Limit Status

Further to the recent announcement (https://x.com/easterncardano/status/2032283002055901696) regarding our determination that Cardano governance does not currently have an active Net Change Limit (NCL), we wanted to provide additional information following questions from our community about why we believe the 350 Million ADA NCL is not active.

The following provides our reasoning for why the governance action with ID “gov_action1m3xx08yv788vfxqh6nfvrjtvmqpwezsy0ggaczctkyjmttc2wmxsq4jsr7q” and titled “Net Change Limit (Epoch 613 to Epoch 713)” needs to be assessed against the constitution and therefore because it did not reach the constitutionality threshold it cannot be considered an active NCL.

Rationale

We have determined that the Constitutional Committee (CC) must assess the constitutionality of Info governance actions (the above NCL was submitted via an Info action). This is based on Article III Section 1.4, which states “The CC shall be limited to voting on the constitutionality of governance actions, including any proposed or contemplated actions contained within “Info” actions.”

This interpretation is reinforced by the deliberate departure from the previous constitution, which explicitly stated: “Because ‘Info’ actions have no on-chain effect and, accordingly, are neither constitutional nor unconstitutional, Constitutional Committee members may not prevent ‘Info’ actions from being recorded on-chain.”

The removal of that exemption in the current constitution, combined with the affirmative language of Section 1.4, reflects a clear authorial intent to bring Info actions within the CC’s review remit. If the author did not intend for the CC to assess the constitutionality of Info actions, there would have been no reason to include Section 1.4, and no reason to remove the previous constitution’s explicit exemption.

As the above NCL Info action only received 4 Yes votes from the CC, it fell below the 67% threshold required to be considered constitutional.

Counterarguments

While we have not seen any official counterarguments from other CC members, we have observed social media posts that may relate to the opinion of some CC members. The following are some of the sections that have been referred to about whether an NCL Info action needs to be assessed as constitutional to be considered active.

Article III Section 1.1 states “A CC shall be established as the branch of Cardano’s on-chain governance process that ensures governance actions to be enacted on-chain are consistent with this Constitution.”

It has been suggested that this paragraph implies that the CC’s responsibility is to ONLY assess governance actions that are “enacted” on-chain, which Info actions are not. This would be a reasonable interpretation of this paragraph if it was the only entry, but it is not stated in isolation. As stated above, if the intention of the author was to exclude Info actions from requiring constitutional assessment, there would be no reason to include Section 1.4. The two provisions are best read together: the CC ensures governance actions enacted on-chain are constitutional (Section 1.1), and separately assesses the constitutionality of Info actions (Section 1.4).

Guardrail TREASURY-01a states “A Net Change Limit for the Cardano Treasury’s balance per period of time must be agreed by the DReps via an on-chain governance action with a threshold of greater than 50% of the active voting stake”

This guardrail is being used to argue that only DReps need to approve an NCL, as it doesn’t reference the CC. This argument however implies that the guardrail should be considered in isolation from the rest of the constitution. The purpose of the guardrail is to define the DRep threshold for it being considered passed (i.e. >50%). The guardrail still requires agreement “via an on-chain governance action,” which means the other constitutional provisions governing governance action approval (including CC review) as required by the current constitution continue to apply.

Timing

The ECC’s decision to pause voting during the constitutional transition period was explained publicly in advance. That decision was unrelated to the outcome of either NCL action, and any suggestion that the ECC deliberately withheld votes to prevent treasury withdrawals from passing is without foundation.

The ECC was not aware that other CC members did not intend to vote on the 350 Million ADA NCL, and could not predict the outcome of either that action or the 300 Million ADA NCL that followed. We note that had the ECC intended to block the NCL, the appropriate mechanism would have been to vote No, not to abstain or to pause voting on procedural grounds.

Coordination

This situation highlights the issue of the lack of professional coordination in Cardano governance, where DReps, CC members and the broader community can discuss constitutional issues that may present themselves.

While we have observed some discussion on social media platforms (such as X), this does not provide effective coordination. Algorithmically mediated social platforms favour whoever speaks loudest, and whoever has the most followers. That’s not deliberation. There is no way to ensure that anyone sees posts from anyone. This doesn’t create the conditions to conduct an appropriate constitutional debate.

Independently of the constitutional questions addressed above, we encourage the Cardano community to explore more explicit and robust means for setting Net Change Limits, mechanisms that remove ambiguity about the threshold, process, and constitutional review requirements that apply. The current situation demonstrates that the existing framework lacks the procedural clarity needed to ensure those requirements are consistently understood and met by all governance participants.

2 Likes

There was no reason however to take such a long time to review the new constitution. It was already up for review for weeks, previous versions even longer, and no other CC member seems to have needed this extended review time.
And even then, you could’ve abstained from the gov action for setting the NCL.
I’m not saying your reasoning about not having a NCL is wrong, I was wondering the same right after the vote and raised my concerns. So waiting so long to come out with this statement is uncalled for.
You guys seem to be lost in a web of technicalities defending your actions, neglecting the way it hurts the Cardano ecosystem.
Being part of the cause of not having a NCL in your view, the right thing to do now is abstaining from all treasury withdrawals until a new NCL is set.

Hi Eastern Cardano Council!

On behalf of Ace Alliance, I will provide our Counterargument of why and how the NCL should be considered in effect. We put this within the Rationale of our vote on the “Amaru Treasury Withdrawal 2026” governance action.

We agree with the assessment that the NCL governance action fell short of the required 67% CC voting threshold necessary for passage, however, we do not believe that it would be just to punish the community for the Constitutional Committee’s failure of coordination.

We have outlined our solution below.

https://ipfs.io/ipfs/QmTVLbVxNjMdX9nXWvU1sKnmJD2yasCWgXEEgfFbh7Pth4

Precedent Discussion

Under Article II.7.3, a Net Change Limit (NCL) must be set for a TWGA to be found Constitutional. Accordingly, we look to the “Net Change Limit (Epoch 613 to Epoch 713)” (gov_action1m3xx08yv788vfxqh6nfvrjtvmqpwezsy0ggaczctkyjmttc2wmxsq4jsr7q) governance action (“350M ADA NCL”).

While the 350M ADA NCL did receive sufficient DRep support, the four Yes and three non-votes by CC members resulted in 4/7 (57%) CC approval. Before evaluating whether this NCL action passed, we must first assess whether a proposed NCL contained in an Info Action is subject to CC review.

The Constitution expressly resolves the question of whether an NCL Info Action is subject to CC review. Within the CCs limited role of voting on the constitutionality of governance actions, the scope of Article III.1.4 includes “any proposed or contemplated actions contained within Info actions.” That provision is directly relevant here, where the NCL Info Action was the proposed mechanism by which the Net Change Limit required under Article II.7.3 would be set. This Info Action, like all governance actions reviewed for constitutionality by the CC, must resolve to a definitive state of constitutional or unconstitutional at the close of voting. Otherwise, Article III.1.4 would have no effect.

As for whether the NCL Info Action passed, the Constitution provides a single method for mapping CC votes to the relevant constitutionality outcome. Article III.1.3 states that no governance action, other than a No Confidence or Update Committee action, may be implemented on-chain without affirmation by the requisite percentage of CC members. For the relevant period, that requisite percentage was set on-chain at 67% through the applicable Update Committee action (gov_action1g7sw0f8e8qa34lppj2erksvzf4j6e9udwaq6efslc8apdqeazygsq2spyyt). This on-chain action established the binding method for translating Yes votes, No votes, Abstentions, and non-votes into a final disposition. The Constitution establishes this cumulative threshold mechanism, and the view of any one CC member does not determine the outcome.

Under ordinary circumstances, this framework would require treating the 350 Million ADA NCL as having failed to achieve the constitutionality threshold. Four Yes votes and three non-votes do not satisfy the 67% requirement. However, the present case is not ordinary. Here, individuals from two of the three non-voting CC seats publicly stated that they did not believe voting on Info Actions was required, and that they considered the 350 Million ADA NCL to be constitutionally valid.

While those statements do not alter the ordinary constitutional rule or create an alternative to on-chain voting, they do bear directly on whether the failure to record votes on-chain reflected substantive opposition to the NCL or a mistaken understanding of their duty to vote. Because an Abstain vote removes a CC member from the calculation’s denominator, the action would have met the 67% CC approval threshold if even one of the three non-votes had been an abstain vote. If a member intends to avoid impacting this adjudication calculation, that member must vote Abstain.

Under these extraordinary circumstances, Ace Alliance will look beyond the NCL Info Action and consider CC member votes on this TWGA. If CC voting meets the constitutionally established threshold on this action, Ace Alliance will defer to this outcome for the purpose of evaluating whether the 350M ADA NCL is constitutional and in-effect.

Counterargument Discussion

A valid counterargument is that the Constitution does not authorize displacing on-chain voting results to reconsider governance action outcomes. On that view, our constitutional framework requires votes to be cast through the prescribed process, and neither an individual CC member, nor the CC collectively, may depart from that framework to reconstruct votes after the fact. Our constitutional system of governance is designed to operate through recorded governance actions and votes, and considerable mischief can be done by governance actors who seek to arbitrarily reconsider previously adjudicated outcomes. This argument is persuasive, and under ordinary circumstances it would be the prevailing view.

Under these unusual circumstances, however, we must balance other significant interests, including that all users of the Cardano Blockchain shall be treated fairly and impartially, taking into account the collective desires of the Cardano community under Article I.1.9. Here, it would be plainly unjust to allow the Cardano Community to suffer for the inaction of members of the Constitutional Committee. Under these facts, this consideration weighs heavily in favor of recognizing that the non-votes at issue reflect a mistaken view of voting obligations, and not opposition to the NCL. This measure is necessary to mitigate further harm, to avoid imposing the consequences of admitted procedural neglect on the proposal’s submitters and the community as a whole, and not a rejection of the constitutional voting framework.

Accordingly, Ace Alliance will treat the 350M ADA NCL as constitutional for purposes of this, and any other TWGA submitted pursuant to this 350M ADA NCL, so long as this action meets the required 67% CC affirmation. At the same time, we emphasize that this is an extraordinary, and not normative measure. CC members have a constitutional duty to cast votes on all governance actions for which their constitutional role is implicated, which explicitly includes Info Actions under Article III.1.4.

Separately, we encourage the Cardano community to explore more explicit and robust means for setting Net Change Limits.

Very nice rational. Thank you all

Also I think it’s worth noting on the section here

Coordination and collusion are only thinly separated! I do not at all mind a world where my CC members don’t have an idea how the other CC members or DReps are planning to vote.

That is SAFER than higher level coordination that lends itself towards collusion

There is only an NCL if the CC deems it so.

Dissenting within the CC is one mechanism to ensure they are doing their job.

Thanks Adam, we will discuss the arguments made in this and consider them in our further deliberations on this matter.

According to the constitution, the CC must assess the constitutionality of info actions only when they are referring to “enactable” governance actions. This is clearly stated in section 1.4: […] including any proposed or contemplated actions contained within “Info” actions.

This last statement does not instruct CC to vote on EVERY info actions; but only those that contain a governance action for which constitutionality must be assessed. Indeed, as per section 1.1, the role of the CC is restricted to evaluating actions that have an effect on-chain (i.e. can be enacted).

So technically, the CC voting on an info action isn’t evaluating the constitutionality of that info action, but is evaluating the constitutionality of actions referenced in that info action. I would even argue that it is actually unconstitutional for the CC to vote on info actions that don’t contain another governance action, but I digress.

In particular, the concept of NCL does not exist on-chain and has no equivalent action. Thus, an info action establishing an NCL needs no assessment from the CC. It is fully up to DReps.

Where there is ambiguity IMO is in what constitutes an NCL. Nothing in the constitution says that the NCL should be an info action to begin with. As far as it goes, you could pass an NCL as a treasury withdrawal or even a parameter change (which would actually be more appropriate if you think about it…). Historically, info actions have been used, but nothing really tells you what the format should be: should the title contain ‘NCL’? should it be denominated in ADA? Is there a maximum period of time it should cover? etc…

2 Likes

Section 1.1 relates to one of the reasons for having a CC, that is to “ensure” that GAs that need “to be enacted on-chain are consistent with this Constitution.” It doesn’t say exclusively or solely to ensure. Also by stating “including any proposed or contemplated actions contained within “Info” actions.” in Section 1.4 it implies there is more to the role than just on-chain enactable GAs, otherwise there would be no reason to include that part.

The previous constitution provided more precise wording about whether the CC can assess the constitutionality of Info GAs, so if the intent was to retain the same scope as the previous constitution, there would be no reason to change the text. It was a deliberate change for a deliberate reason.

Section 1.4 also states that “The CC shall be limited to voting on the constitutionality of governance actions”. Use of the word “limited” just means they cannot vote on the merits of a GA.