Cardano’s Dijkstra Timeline Faces Governance Risk as Committee Vote Nears Deadline

Cardano’s Dijkstra upgrade has gained a new dependency outside protocol development itself. Intersect says the timeline faces a potential risk of delays if the ongoing Constitutional Committee action fails to secure enough support before its September 1 deadline.

The issue does not involve an existing Dijkstra hard-fork vote. Instead, failure of the committee action could temporarily stall the governance mechanisms Cardano will need as Dijkstra moves from development and testing toward eventual activation.

Constitutional Committee Vote Remains Below Both Thresholds

The Update Constitutional Committee 2026 governance action expires on September 1 at 21:44:51 UTC.

According to Intersect’s August 28 snapshot, DRep voting progress stood at 64.24% against the required 67%, while SPO progress was 35.3% against a 51% threshold. Both thresholds must be reached for the action to pass.

Four current Constitutional Committee terms are approaching expiration. If replacements are not enacted in time, the committee would fall from seven active members to three, below Cardano’s committeeMinSize requirement of five.

That would not stop Cardano from producing blocks or processing transactions. The impact would be limited to governance actions requiring Constitutional Committee approval.

Hard Fork Initiation actions, protocol parameter changes, treasury withdrawals and constitutional updates would be unable to progress through the full ratification process until the committee is restored.

Update Committee and Info Actions would remain available, providing a path to restore the committee without interrupting normal network operation.

Intersect Connects the Vote Directly to Dijkstra

The Dijkstra connection became explicit in Intersect’s August 28 development update.

Intersect reported that upcoming node releases are expected to unlock early Dijkstra functionality for testing, but warned that current timelines face a potential risk of delays because of the Constitutional Committee vote.

The dependency sits further along the upgrade path.

Input Output is preparing constitutional changes covering new parameters and guardrails required for Dijkstra. Those changes will need to progress through Cardano’s governance framework before the corresponding protocol changes can move toward activation.

A Hard Fork Initiation governance action will also eventually be required to activate the new era on mainnet. No such Dijkstra action has yet been submitted.

This distinction matters. The current committee vote is not blocking a Dijkstra hard fork already waiting for approval. It could instead create a bottleneck when technical work reaches the point where constitutional changes, protocol parameters and the eventual hard fork require governance ratification.

Technical Progress and Governance Readiness Are Now Separate Timelines

Development of Dijkstra can continue regardless of the outcome on September 1.

Dijkstra is Cardano’s next ledger era and the first phase of a broader protocol upgrade path that includes Nested Transactions and Linear Leios. Ouroboros Peras is planned separately for a later phase.

Upcoming node releases can expose early Dijkstra functionality for testing while engineering teams continue implementation across the protocol and supporting infrastructure. In that sense, a failed committee vote does not stop developers from building Dijkstra.

Governance readiness is different.

If the Constitutional Committee falls below five active members, Cardano would need to restore it before committee-dependent governance actions could be ratified. A new Update Committee action can provide that recovery path, but it would require another governance process and sufficient DRep and SPO support.

The September 1 deadline therefore separates two tracks in Cardano’s next upgrade cycle. Dijkstra can continue moving toward technical readiness, but without a functioning Constitutional Committee, governance readiness could fall behind it.