Dijkstra-era Hard Fork CIP Shortlist

The following is a draft Info Action designed to solicit the Cardano community for prioritization on CIPs for the Dijkstra Hard Fork (est. Q1-Q2 2027).

Dijkstra-era Hard Fork CIP Shortlist

Abstract

This Info Action presents a list of possible Cardano Improvement Proposals (CIPs) to be included in the scope of the Dijkstra-era hard fork (expected as Protocol Version 12). The linked survey will capture dRep preferences on each of these items for voting and prioritization. Note that voting for/against this action as a whole indicates approval/disapproval of the process, not of the associated changes.

Motivation

The Dijkstra-era hard fork is expected to include a set of protocol changes drawn from a short list of candidates for community consideration.

This Info Action provides a clear, transparent, and standardized way for dReps to vote on those changes and to indicate their relative priorities for inclusion in the Dijkstra-era hard fork. It does not propose a definitive list.

Interpretation of the formal governance vote

The formal YES / NO / ABSTAIN vote on this Info Action should be interpreted as follows:

  • YES: I support this process
  • NO: I do not support this process.
  • ABSTAIN: I decline to take a position on this process.

Votes on the actual CIPs should be recorded in vote response metadata using the format described in CIP-179.

Candidate CIPs

The following candidate CIPs are proposed for dRep voting and prioritization in the Dijkstra era:

Parallel reward-sharing incentive ballot

Several of these CIPs are also being voted on through a separate ballot using Ekklesia.

Those CIPs are:

The scope of that ballot and this survey overlap, but can be more easily understood when framed in the following way:

  • Incentives ballot - Do you support these CIPs?
  • Dijkstra shortlist - Which CIPs should be prioritized for Dijkstra specifically?

Nature of the outcome

This survey is advisory and informational. It is intended to capture dRep sentiment on the listed candidate CIPs and provide a clear public signal regarding both support and relative priority for inclusion in the Dijkstra-era hard fork.

The outcome of this survey does not by itself enact any CIP or confirm any work. Final releases still depend on implementation readiness, development, testing, and release coordination.

dReps are invited to review the candidate CIPs presented in this Info Action and cast their votes accordingly. The resulting tallies should be used as a transparent public signal to help guide Dijkstra-era hard fork composition and prioritization.

Disclaimer on survey results

Because the poll results for this survey reside in linked CIP-179 metadata, any interim or early-reported results should be treated as provisional. The results of this survey should not be considered final until the survey has ended and the corresponding responses have been validated and tallied.

2 Likes

Additionally, there are a list of CIPs that are considered “on deck” should they be finalized through the CIP process before the Info Action is submitted:

1 Like

Optimistic constitutionality in it’s current form is a major security risk.

1 Like