> For the complete documentation index, see [llms.txt](https://cardanoupgrades.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://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/23rd-july-2026.md). # 23rd July 2026 #### Agenda 1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/overview/hard-fork-working-group-meeting-minutes/21st-july-2026#action-items-and-next-steps) - Bosko 2. Van Rossem Upgrade Update - Bosko, Sam, Can 1. Enacted on 18th July with \~10 mins gap before the first block 2. SRE & Engineering is closely monitoring the network behavior, especially on the epoch boundary 3. [Dijkstra era hard fork](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era/dijkstra-overview) - Bosko, all 1. Hard fork naming 1. Motion of naming it after Alexander Esgen, with adding In Memoriam section to eternalize others who sadly passed away in recent months/years 2. Scope 1. [Product committee - Dijkstra Era: Phased Rollout Plan](https://github.com/IntersectMBO/product-website/blob/master/docs/hardfork-planning/dijkstra.md) 3. CIP 179 - [Tesera application](https://tessera-preview.matthieu-pizenberg.workers.dev/) - Ryan C 1. [Repo](https://github.com/mpizenberg/Tessera) 2. [Context on what now + potential future PR](https://github.com/cardano-foundation/CIPs/pull/1224#issuecomment-4950735776) 4. AOB #### Key materials * Summary * **van Rossem hard fork** * SRE team and engineering teams re-confirmed that they are on standby for at least one epoch to observe whether there will be any issue similar to what happened on the van Rossem enactment epoch boundary * Technical Steering Committee shared their insights on potential causes * **Dijkstra Era hard fork** * Scope * Sam Leathers from the Product Committee gave a transparent walkthrough of [the Dijkstra hard fork phased rollout plan](https://github.com/IntersectMBO/product-website/blob/master/docs/hardfork-planning/dijkstra.md) which opened the way to a good discussion on whats possible within the designated time frame of October 2026 for code completion of Dijkstra era hard fork (primary activation target are **nested transactions**) * Phased rollout plan also lists 2 subsequent intra-era hard forks, one in Q1 2027, one in Q2 2027, where they would activate **Ouroboros linear Leios** and **Ouroboros Peras** respectivelly * Hard Fork working group was informed of that the team behing Dingo node already implemented CIP-23 and CIP-50 * Sebastian will reach out to Dingo and Amaru nodes teams to assess their scoping and future hard fork readiness around the discussed timelines * Potential constitutional changes, both technical and social are carefully considered by the hard fork working group to properly asses their anticipated impact on the timeline * Haskell node team product manager Carlos will attend the next parameter committee call in 3 weeks to further discuss that impact * Timing * The plan for having the first (out of anticipated three hard forks enacted by the end of 2026) remains ambitious which subsequently limits the scope discussion * Prioritization & process * Kevin, Sam and Ryan (Cerkoryn) are continuing the work in order to have meaningful and impactful process for community participation in defining the scope of any future hard forks post first one in Dijkstra era * Next hard fork naming - motion * Motion of "naming the hard fork after Alexander Esgen, with adding In Memoriam section to eternalize others who sadly passed away in recent months/years" took place with 14 attendees voicing their support for it and 1 who didnt vote * Consequential expectation is that there is going to be an info action for naming it Esgen hard fork submitted and that all other respected community members who passed away in recent months/years will be eternalized in the **In Memoriam** section of the governance action * Hard Fork Working group continued to discuss future naming options and how to avoid potential challenges over naming as, unfortunately, there are too many candidate names for too few hard forks * Hard Fork Working Group meetings will continue to happen twice a week, until at least the Dijkstra hard fork scope is set, after which the future meeting cadence will be decided * Hard Fork Working Group communication channels * [Discord](https://discord.com/channels/1136727663583698984/1242097284619960411) — `#wg-hard-fork` * [Weekly bulletins](https://x.com/IntersectMBO) * [Luma calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif) * [Email](mailto:hard-fork@intersectmbo.org) * [Product committee - Dijkstra Era: Phased Rollout Plan](https://github.com/IntersectMBO/product-website/blob/master/docs/hardfork-planning/dijkstra.md) * [Recording](https://drive.google.com/file/d/1msY_IuZ1pRUexj_wz0utxP8UZnAPD9Uc/view?usp=drive_link) * [Transcript](https://docs.google.com/document/d/1jF2vztkwE1vIjM-bGWAqsUrLfS-H8IIsWGDKLmqrAdI/edit?usp=drive_link) * [Chat](https://drive.google.com/file/d/1aBCH0QDWsas4IOv1zBtA83nad76EZ0VO/view?usp=drive_link) #### **Action items and next steps** * **Carlos:** Attend the next parameter committee call in 3 weeks to further discuss the impact on constitution and parameters for the Dijkstra era hard fork * **Sebastian:** Reach out to Dingo and Amaru nodes teams to assess their scoping and future hard fork readiness around the discussed timelines * **Geoff:** Attend the Technical Steering Committee meeting on 29th July to present the scope for Dijkstra and plans for delivery * **Kevin/Sam L/Ryan C W:** Draft the decision making and prioritization process for future hard forks * **Bosko:** Continue creating supporting structure and relevant documentation within the hard fork working group GitBook space under Technical Steering Committee * **Tex:** Create ecosystem dependency mapping document(s) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/23rd-july-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.