Chang Timeline & Dependencies

The following timeline is indicative, based on currently available information and is subject to change.

Timeline is based on current velocity of development, scope changes and testing outcomes. Information is accurate as of 10th June 2024


The information in this timeline is explained in the following Chang Upgrade, Forecast Release Dates and Hard Fork Dependencies sections.

Chang Upgrades

The Chang upgrade will stagger the release of governance functionality, easing adoption and onboarding for those with new or additional roles in governance.

  1. Chang Upgrade #1 Will deploy governance features to Cardano and entre the technical bootstrapping phase as described in CIP-1694

  2. Chang Upgrade #2 Moves CIP-1694 out of technical bootstrapping phases and unlocks the final features of on-chain governance including DRep participation and treasury withdrawals

Further information on CIP-1694 and the interim bootstrapping period is available.

Forecast Technical Release Dates

The following dates have been provided by the core Cardano development teams based on current velocity of development, scope changes and testing outcomes.

These dates do not include social or community readiness.

It is possible social or community dependencies will not yet have been met, therefore impacting the final hard fork dates.

  • 8.12 - target 10th June

  • 9.0 (8.12) - Mainnet candidate target 17th June

  • Bump to 9.0 - Community driven target 17th July

Latest release information and notes can be found here at the cardano-node releases github page.

Hard Fork Dependencies

The above timeline indicatively shows the high-level activities and dependencies required for the Chang hard fork. These are broken down with acceptance criteria and status below.

Items which need to be completed or at a suitable point prior to initiating the hard for combinator event for Chang.

ItemAcceptance Criteria Current Status

Node 9.0

Suitable candidate for mainnet release

In progress, target 17th July

Node 9.0 (8.12)

Suitable candidate released in Preview environment, to be available for community testing for X days

In progress, target 17th June

Dquadrant Chang Testing

Completion of testing, no major issues outstanding

In Progress

Tweag Guardrails Script Audit

Completion of script audit, no major issues outstanding

In Progress

Tweag Constitutional Committee Identity Script Audit

Completion of script audit, no major issues outstanding

In Progress

GovTool Complete

Fully deployed and ready for new governance era

In Progress

DRep Pioneer Programme

Programme on track, no major issues reported.

In Progress

Constitutional Committee Genesis File

Completed and ready for inclusion in node

Not Started

Technical Readiness

A ‘roll-call’ from the technical teams, performance & benchmarking and issue management that all teams have signed off on the release candidate and that no high severity issues are outstanding

ItemAcceptance CriteriaCurrent Status

Technical team checklist/roll call

Technical checklist, attestation of quality and readiness from core delivery teams

Not started

Performance and Benchmarking

Suitable performance and benchmarking tests completed

In Progress

High severity issues

No high-level issues outstanding on cardano-node related to Conway

None currently reported

Community readiness

Qualitative feedback and sentiment from key community committees, hubs and working groups on their readiness for the hard fork.

AreaAcceptance CriteriaCurrent Status

Hard Fork Working Group

Poll of working group members

Not Started

Technical Steering Committee

Poll of committee members & continuity suppliers

Not Started

Parameters Committee

Poll of committee members

Not Started

Open Source Committee

Poll of committee members

Not Started

Membership and Community Committee

Poll of committee members

Not Started

Constitutional Committee

Poll of committee members

Not Started

Intersect Hubs

Poll of each membership hub

Not Started

Stake-Pool Operators (SPOs)

Poll at SPOs monthly town hall

Not Started



Not Started

Ideally, a majority of SPOs and Exchanges will run the latest node version prior to hard fork initiation.

All of the elements above are required before certainty can be given to the Chang hard fork date.

As these dependencies start to complete or provide compelling completion dates the window and date for Chang hard fork will become clearer.

More information on the Major Release Process is also available. A frequently asked questions page, related to Chang and hard forks is also being updated on the knowledge base regularly.

To contribute to testing or provide feedback please visit the SanchoNet website, as many features are already available for testing.

Last updated