> 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/28th-july-2026.md). # 28th July 2026 #### Agenda 1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/overview/hard-fork-working-group-meeting-minutes/23rd-july-2026#action-items-and-next-steps) - Bosko 2. Van Rossem Upgrade Update - Bosko, Sam, Can 1. On the last epoch boundary, SRE\&Engineering confirmed there was no delay on block producing 2. Engineering team is nevertheless doing the investigation into what made first block in the HF so slow to be produced - Alexey, Carlos 3. [Dijkstra era hard fork](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era/dijkstra-overview) - Bosko, all 1. Hard fork naming 1. **23rd July** motion - Recommend naming it after Alexander **Esgen**, with adding In Memoriam section to eternalize others who sadly passed away in recent months/years 1. Fabian **von Bergen** - there is already the [info action](https://cardanoscan.io/govAction/gov_action1fzatpjn3e3r09mjzzfptznef9wxg8q4a5uraq04xvfjyhmfzhzfsqqgfc9h) 2. Steven **Lupien** 3. Gregg **Morgan** aka [@bone\_pool](https://x.com/bone_pool) 4. Sean **Davies** 2. Scope 1. [Product committee - Dijkstra Era: Phased Rollout Plan](https://github.com/IntersectMBO/product-website/blob/master/docs/hardfork-planning/dijkstra.md) 3. Node diversity 1. Haskell 2. Amaru (Rust) 3. Dingo (Go) 4. TSUNAGI (Zig) 5. Gerolamo (TypeScript) 6. Dolos (Rust) 7. Turbocardano (C++) 8. Razor (.NET) 4. AOB #### Key materials * Summary * **van Rossem hard fork** * Carlos from the Haskell node team tested scenarios with forking priavte testnet environment and none of them produced even similar outcome to the block producing delay on the van Rossem enactment on mainnet * At the last epoch boundary, block was created at only \~15 seconds into the new epoch which is well within the expectations, CPU and memory were looking steady * **Dijkstra Era hard fork** * Scope * Phased rollout plan consider 3 stages with each having key feature in it enabled, nested transactions, linear leios and peras respectively * CIP-50 implementation that was done by the external contributor Jared Corduan is expected to be merged in the codebase * CIP-23 is likely to be included in the 2026 plan too * Jeff from IO will present the Dijkstra era hard fork scope, as suggested by the Product Committee, to the Technical Steering Committee on the weekly call on 29th July * The expectation is to have the first Dijkstra era hard fork scope freezed by the end of this week, so 31st July * Constitutional changes * It was considered that that the constitutional changes needed for this hard fork should happen after the hard fork enactment * Socialization of the above mentioned constitutional changes should begin as soon as its possible * Timing * The goal of the Haskell node team is to deliver Phase 1 & Phase 2 (Nested transactions and Leios) on mainnet by the end of 2026 * 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 * Hard Fork Working Group acknowledges the fact that there is an [info action](https://cardanoscan.io/govAction/gov_action1fzatpjn3e3r09mjzzfptznef9wxg8q4a5uraq04xvfjyhmfzhzfsqqgfc9h) submitted on chain to name the hard fork after Fabian **von Bergen** * It is also true that other info actions with the goal to have hard fork named after other community members who sadly passed away can be expected * Hard Fork Working Group will adhere to the outcome of the motion held on the meeting on [23rd July](https://cardanoupgrades.docs.intersectmbo.org/overview/hard-fork-working-group-meeting-minutes/23rd-july-2026#key-materials) where it was decided to name it after Alexander **Esgen**, with adding In Memoriam section to eternalize others who sadly passed away in recent months/years * In Memoriam section have these names considered: * Fabian **von Bergen** - there is already the [info action](https://cardanoscan.io/govAction/gov_action1fzatpjn3e3r09mjzzfptznef9wxg8q4a5uraq04xvfjyhmfzhzfsqqgfc9h) * Steven **Lupien** * Gregg **Morgan** aka [@bone\_pool](https://x.com/bone_pool) * Sean **Davies** * Hard Fork Working Group invites the whole community to give feedback and consider other names to be added as all Cardano community contributors deserve posthumous recognition of their impact * Node Diversity * Mapped ecosystem nodes so far: * Haskell * Amaru (Rust) * Dingo (Go) * Dugite (Rust) * TSUNAGI (Zig) * Gerolamo (TypeScript) * Dolos (Rust) * Turbocardano (C++) * Razor (.NET) * All node teams will be invited to the hard fork working group meetings * Hard Fork Working Group will likely reduce the number of meetings to once a week or once every 2 weeks, starting from next week, after the Dijkstra era hard fork scope is expected to be set by the end of this week * 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/1Pu5Ih47JkXy0lQ38exEIV622SnNRN1Rh/view?usp=drive_link) * [Transcript](https://docs.google.com/document/d/1ZaRieaxH-VkVRin6_YHTUPvo3ZgYzRaXhgmav-8RG4g/edit?usp=drive_link) * [Chat](https://drive.google.com/file/d/1MFZKDC84Kvrjsklt2HFf3fRsJsPOFyWF/view?usp=drive_link) #### **Action items and next steps** * **Bosko:** Send invitations for the Hard Fork Working Group meetings to all listed node teams * **Carlos:** Attend the next parameter committee call in 2 weeks to further discuss the impact on constitution and parameters for the Dijkstra era hard fork * **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/28th-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.