Chang Timeline & Dependencies
Any dates or windows provided in this Chang hard fork timeline are provided as estimates, and approved by the hard fork working group.
These are based on factors such as velocity of development, testing outcomes, issues raised, and critical mass indicators.
Information on this page was last updated on 19th June 2024
Intersect plays the role of coordinator, as a functional servant-leader on behalf of the community and delivery teams working on hard fork activity. The functional teams within Intersect will work with the various committees, working groups, and delivery teams, relaying information here on the knowledge base. Ultimately the date for the hard fork is directly influenced by the community fulfilling the requirements detailed below.
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.
Chang Upgrade #1 Will deploy governance features to Cardano and enter the technical bootstrapping phase as described in CIP-1694 Bootstrapping Phase
Chang Upgrade #2 Moves CIP-1694 out of technical bootstrapping phase and unlocks the final features of on-chain governance including DRep participation and all governance actions
Further information on CIP-1694 and the interim bootstrapping period is available.
Chang Upgrade #1
In the lead-up to Change Upgrade #1 the following sequence of events will occur, driven by community participation and adoption.
| Step | Environment | Owner |
|---|---|---|
Node version 8.12 will be released (may only be a pre-release) | N/A | Delivery Teams |
Benchmarking and performance testing will be conducted on node version 8.12 | N/A | Delivery Teams |
Node passes benchmarking and performance testing (D1) | N/A | Delivery Teams |
Node 9.0 is Released | N/A | Delivery Teams |
Preview upgraded to 9.0 and hardforked | Preview | Delivery Teams |
No critical issues outstanding on Cardano-Node (D1) | Preview | Delivery Teams |
SPOs, Exchanges and DApps will be asked to upgrade to 9.0 on Pre-Production and Mainnet (D2) | Pre-Production & Mainnet | Community |
Parameters & final genesis file will be prepared (required for 9.01) | N/A | Delivery Teams |
SPOs, Exchange and DApps will be asked to upgrade to 9.01 Pre-Production and Mainnet (a full upgrade may not be required) | Pre-Production & Mainnet | Community |
Critical mass indicators are met, 70% SPOs and 80% Exchange liquidity (D3) | Pre-Production & Mainnet | Community |
Steps for Chang #2 upgrade will be released after completion of Chang #1 upgrade.
Cardano Environments
Preview: Environment to test the latest functionality before release.
Pre-Production: Environment that matches mainnet configuration, long-term and stable environment for final-stage integration/upgrade testing.
Mainnet: Our production environment – the actual network the Cardano community uses every day.
Release Forecast
The following timeframes have been provided by the core Cardano development teams based on current velocity of development, scope changes and testing outcomes.
The following dates are purely engineering estimates provided by the delivery teams, approved by the hard fork working group for sharing. Hard fork dates will be known once dependencies are met and the community fulfils critical mass indicators
8.12 - mid June
9.0 - end of June
9.01 - early 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 the dependencies, as agreed by the hard fork working group, which need to be completed or at a suitable point prior to initiating the hard for combinator event for the Chang upgrades.
| Item | Acceptance Criteria | Current Status |
|---|---|---|
Node 9.0 | Suitable candidate released in Preview environment, to be available for community testing and upgrade | In progress |
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 |
Core Governance Tooling (GovTool, CC Portal, etc.) | Governance tools finished developement, testing and deployed across environments | In Progress |
Major Hardware Wallet Updates (Ledger and Trezor) | Conway era development completed, tested, audited and included in offical release | In Progress |
DRep Pioneer Programme | No major programme issues reported. 15 initial DRep Workshops scheduled (upcoming workshops) | In Progress |
Constitutional Committee Genesis File | Completed and ready for inclusion in node 9.01 | In Progress |
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
| Item | Acceptance Criteria | Current 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 |
*Issues are tracked here on the Cardano-node Github repository. Issues are marked by severity by the delivery teams. A severity 1 or 2 issue may prevent hard fork until resolved. Most lower-level severity issues will not prevent a hard fork, this is reviewed on a case-by-case basis.
Community readiness
Qualitative feedback and sentiment from key committees, hubs, and working groups on their readiness for the hard fork.
As well as this feedback a number of critical mass indicators need to be met in order for the community to smoothly enact a hard fork. This is primarily driven by SPOs and exchanges, although other key dependent and supportive tooling will also be monitored.
| Area | Acceptance Criteria | Current Status |
|---|---|---|
Hard Fork Working Group | Poll of working group members | 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 |
Civics Committee | Poll of committee members | Not Started |
Intersect Hubs | Poll of each membership hub | In Progress |
Stake-Pool Operators (SPOs) | 75% SPOs running Node 9.01 on mainnet | Not Started |
Exchanges | Majority of exchanges by liquidity (circa 80%) running hard fork node | Not Started |
Shortly after node 9.0 has been released an attestation page for community and ecosystem readiness will be launched to update progress on dependent tooling and these critical mass indicators.
Any dates or windows provided in this Chang hard fork timeline are provided as estimates, and approved by the hard fork working group.
These are based on factors such as velocity of development, testing outcomes, critical mass indicators, and issues raised.
Information on this page was last updated on 19th June 2024
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
