Cardano (ADA) is approaching a critical governance deadline on September 1, when a vote to seat four elected Constitutional Committee members expires. The outcome matters, as failure would reduce the committee from seven active members to three, below Cardano’s required minimum of five members.

According to CardanoScan, average delegated representative (DRep) support stood at 41.7% on August 25, compared with the 67% threshold required for approval. Stake Pool Operator support was even further behind at 12%, against a required 51%.

That leaves gaps of 25.3 percentage points for DReps and 39.0 points for SPOs before the vote expires in epoch 653.

Support has Improved, but the Deadline is Tight

Earlier readings show support moving higher. On August 17, a GovTool snapshot showed DRep backing at 32.46% and SPO support at 1.95%. Intersect later reported figures of 37.9% and 7.93% on August 21.

The readings come from different governance interfaces, so they should not be treated as directly comparable point-for-point. Still, they show that voting activity has increased as the deadline approaches. The central issue is whether enough active stake moves before September 1.

Why the Committee Vote Matters

The proposal would formally install four winners from Cardano’s 2026 Constitutional Committee election before four existing members leave office.

If the action expires without approval, only three committee members will remain. Under CIP-1694, that would leave the committee below its five-member floor and prevent it from ratifying governance actions that require committee approval.

That would not stop Cardano itself. Blocks would still be produced, transactions would continue, and users could still move ADA or interact with decentralized applications. The disruption would instead affect governance.

Also read: Cardano Activates van Rossem Hard Fork Through Full On-Chain Governance

Cardano Would Still Have Recovery Options

An undersized committee would not make the system permanently unusable. Intersect has said Info Actions and Update Committee actions would remain available, providing mechanisms to restore committee membership. CIP-1694 also exempts motions of no confidence from committee approval.

However, rebuilding the committee would require another governance process and could delay decisions that depend on Constitutional Committee ratification.

Dijkstra Could Also Be Affected

The vote arrives as ADA prepares for the Dijkstra era, which is expected to include technical developments such as Nested Transactions, Linear Leios and Peras.

According to Intersect, a break in committee continuity could slow progress toward the planned Dijkstra hard fork.

The practical takeaway is simple: Cardano’s network would keep functioning even if the vote fails, but its governance system could temporarily lose part of its decision-making capacity. With DRep support at 41.7% and SPO support at 12.0%, September 1 remains the decisive date. Turnout, rather than network performance, is the immediate risk for ADA holders.

FAQs:

1. What is Cardano voting on before September 1?

Cardano is voting to formally seat four elected members of its Constitutional Committee. The action must pass before four current members leave office.

2. How much support does the proposal currently have?

According to the latest figures cited, DRep support stands at 41.7% against a required 67%. SPO support is at 12%, compared with the 51% threshold.

3. What happens if the Cardano governance vote fails?

The Constitutional Committee would fall from seven active members to three, below the required minimum of five members. Committee-dependent governance actions could then face a temporary ratification bottleneck.

4. Would Cardano stop working if the vote fails?

No. Block production, ADA transfers and decentralized applications would continue operating normally. The impact would be concentrated on governance rather than network functionality.

5. Could the vote affect Cardano’s Dijkstra hard fork?

According to Intersect, a break in committee continuity could slow the path toward the planned Dijkstra era. It would not necessarily cancel the upgrade, but governance delays could affect its timeline.