> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/cardano-facilitation-services/cardano-development/cardano-hardforks-and-upgrades.md). # Cardano hardforks and upgrades {% hint style="info" %} This page is written on behalf of the Hard Fork working group, the information contained is subject to change and amendment by the working group at any time. {% endhint %} To view details on Cardano Upgrades facilitated by Intersect Hard Fork working group visit the details space below {% content-ref url="/spaces/fG95RnHsh9rCfE922MpZ" %} [Cardano - Upgrades](https://cardanoupgrades.docs.intersectmbo.org/) {% endcontent-ref %} *** The term *hard fork* describes a radical change in the blockchain: a change from one protocol to another, for example. In most blockchains, a hard fork indicates block changes or a change to their interpretation. Cardano initiates hard forks in a unique way, instead of implementing radical changes, through a hard fork combinator event, there is a smooth transition to a new protocol while saving the history of the previous blocks. Intersects role is to coordinate this activity on behalf of the community. This requires collaboration between Intersect members, users of Cardano, and suppliers and builders across the ecosystem. Once a capable, updated node is available there are a series of required activities to test and promote into use and mainstream adoption, via a hard fork. These activities will be coordinated by the Hard Fork working group, which in turn reports into the Technical Steering Committee at Intersect. To learn more about hard forks please read the Cardano Docs article, [here](https://docs.cardano.org/learn/about-hard-forks/). Further information, and an overview of the last major hard fork, Vasil, can also be found on [here](https://docs.cardano.org/cardano-testnet/about/testnet-introduction/) Cardano Docs and previous[ state-of-play updates](https://iohk.io/en/blog/posts/2022/06/20/vasil-upgrade-the-state-of-play/). ## Cardano Upgrades Further details and attestations of community readiness for major upgrades such as hard forks can be found in our dedicated [Cardano Upgrades](https://cardanoupgrades.docs.intersectmbo.org/) space. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intersectmbo.org/intersect-knowledge-base/cardano-facilitation-services/cardano-development/cardano-hardforks-and-upgrades.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.