Chang upgrade #1 - Dependencies & Timeline
This page outlines high-level the dependencies and context for the Chang #1 hardfork.
Last updated
Was this helpful?
This page outlines high-level the dependencies and context for the Chang #1 hardfork.
Last updated
Was this helpful?
Any dates or time windows provided are estimates.
These are based on factors such as velocity of development, testing outcomes, issues raised, and critical mass indicators.
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.
The 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
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 and the interim bootstrapping period is available.
In the lead-up to Change Upgrade #1 the following sequence of events will occur, driven by community participation and adoption.
Node 9.0.0 is released
IOG Core Team
Complete
Parameters & final genesis file will be prepared (required for 9.1.0)
IOG Core Team
Complete
Node 9.1.0 is released
IOG Core Team
Complete
Preview infrastructure upgraded to Node 9.1.0
Community
Complete
Preview hardforked with Node 9.1.0
Community
Complete
PreProd Infrastructure (SPOs, Exchanges, wallets, dApps, etc) upgrade to 9.1.0 and test.
Community
In Progress
Mainnet Infrastructure (SPOs, Exchanges, wallets, dApps, etc) upgrade to 9.1.0.
Community
In Progress
PreProd critical mass indicators met to enable hardfork.
Community
In Progress
Mainnet critical mass indicators met (70% SPOs and 80% Exchange liquidity upgraded and ready with 9.1.0).
Community
In Progress
PreProd hardforked with Node 9.1.0
Community
In Progress
Mainnet hardforked with Node 9.1.0
Community
In Progress
Steps for Chang #2 upgrade will be mapped after completion of Chang #1 harfork.
Node 9.1.0 genesis file preparations
Parameters Committee, ICC
Complete
DQuadrant Chang Testing
DQuadrant
Completion of testing for all new components, no major issues outstanding
Complete
Tweag Guardrails Script Audit
Tweag
Completion of script audit, no major issues outstanding
Complete
Tweag Constitutional Committee Identity Script Audit
Tweag
Completion of script audit, no major issues outstanding
Complete
Core Governance Tooling (GovTool, CC Portal, etc.)
In yon Networks, Bloxico, DQuadrant
In Progress
Major Hardware Wallet Updates (Ledger and Trezor)
Vacuum Labs
Complete
9.0.0 vs Node 9.1.0Node 9.0.0 contains all the new Conway functionality and is fully capable of full governance.
Node 9.0.0 will not be the final node version for Preview, PreProd or Mainnet, as it will not have the correct configuration files, known as genesis files.
The genesis files specify things like protocol parameters and importantly the credentials for the interim constitutional committee.
Splitting Node 9.0.0 and Node 9.1.0 allows users to test all the new Node code across networks before having the final genesis files prepared.
Preview: Acts as a preview for newer Node versions, can be unstable.
Pre-Production: Environment that matches mainnet configuration, long-term and stable environment for final-stage integration/upgrade testing.
SanchoNet: An unstable temporary network for governance testing.
Mainnet: Our production environment – the actual network the Cardano community uses every day.
The plan is to maintain SanchoNet in full governance mode.
To give everyone a way to test full governance on Sancho whilst testing bootstrapping on Preview.
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 .
ICC members have created all cold credentials, Parameters committee ratifies the parameter settings ()
Governance tools finished development, testing and deployed across environments ()
Conway era development completed, tested, audited and included in official release ()
While hardforking Preview Network into and keeping it there for the foreseeable
More information on the is also available. A page and page related to the Chang hard fork is also being updated on the knowledge base regularly.
