> 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/14th-july-2026.md). # 14th July 2026 #### Agenda 1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/9th-july-2026#action-items-and-next-steps) - Bosko 2. Van Rossem Upgrade Update - Bosko, all 1. Ratified on 13th July, will be enacted on 18th July 1. Reimburse Ikigai TWA expired without reaching 67% threshold 2. \~93-96% blocks with protocol v11 produced, exchanges at 84.19% readiness 3. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724) 4. Comms - Ian / Larisa 5. Technical support before and after hard fork enactment - Bosko, Can 3. [Dijkstra era hard fork](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era/dijkstra-overview) - Bosko, all 1. Scope 1. [Shortlist doc](https://docs.google.com/document/d/1YN_Rn3RaY26JHlnhsNU-rQR3tnrihGAp7QHQcBrtEWQ/edit?tab=t.0#heading=h.3f1lcd69byw6) (the only other one that is not mentioned here and is mentioned elsewhere is CIP-151) 2. Must haves for v12 3. Could haves for v12, potentially intra era v13 4. Delayed to full era v14 2. Timeline windows (depending on the scope) 1. Q4 2026 2. Q1 2027 3. Q2 2027 3. CIP 179 - [Tesera application](https://tessera-preview.matthieu-pizenberg.workers.dev/) - Matthieu P, Thomas L, 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** * Ratified on 13th July (643), will be enacted on 18th July (644) * Initially defined bridge call seems to be not working so another one should be scheduled * **Dijkstra Era hard fork** * Scope * Different scope sources collected so far are all similar * All of them have big key features listed * Most of the difference stems from the wishlist scope candidates * Timing * There are different high level time windows where Dijkstra full era hard fork can land and it will be heavily affected with scope * Q4 2026, Q1 2027, Q2 2027 * Prioritization & process * There is no process defined, aligned and agreed * Drafting it should be happening in parallel with freezing the scope of the first next hard fork, full era Dijkstra one * Aiming to have hard fork happening by the end of 2026 implies very conservative approach to the scope freeze, so only absolute necessities should go in * Other items could go to the next intra-era hard fork or the future full era (which should respect the process that is yet to be defined) * Adding all items from the CIP shortlist would likely result in a delay and having the hard fork in Q2 2027 at best, likely later * Haskell node team is invited to give a walkthrough of the scope they are working against to help make decisions on freezing the scope as soon as possible, by the end of the month * CIP-23 was mentioned as Dijkstra scope candidate as a long waited implementation and Haskell team will come back with whats meaningfully possible to make progress against the current timeline * 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) * [van Rossem readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true) * [Recording](https://drive.google.com/file/d/1NGhqjVlTJbtRMbc2sXC_XMlHXuTgixC9/view?usp=drive_link) * [Transcript](https://docs.google.com/document/d/1StZZ-cAVGsHn16yLPQjnShLg6_qA0QUUHfaprfjXyLY/edit?usp=drive_link) * [Chat](https://drive.google.com/file/d/1fQK4mCzxHfgM539SE4ZUoyxk1CrWrGUm/view?usp=drive_link) #### **Action items and next steps** * **van Rossem hard fork** * **Bosko:** Create the new bridge link call (one public and one internal) to be available during and after van Rossem hard fork enactment time window * **Dijkstra Era hard fork** * **Geoff/Carlos/Alexey:** Give a walkthrough of the scope being worked against by the Haskell node team(s) on the next hard fork working group meeting on 17th July * **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/14th-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.