> 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/5th-may-2026.md). # 5th May 2026 #### Agenda 1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/30th-april-2026#action-items-and-next-steps) - Bosko 2. Node v11 readiness - Sam/Ramsay/Jeff 3. [Van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1) - Bosko, all 1. [Readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true) 4. van Rossem comms - Ian / Larisa 1. [Key dates and events for van Rossem upgrade - April, May, June 2026](https://docs.google.com/document/d/1teReTBNeM-t5-LryJJUeLHTHy9B4RDD6AWHwmWJC8f8/edit?usp=sharing) 5. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724) 6. Incident RACI (van Rossem) - Bosko 7. Plutus Cost Model - Ryan 8. AOB #### Key materials * Summary * Node version 11.0.1 is expected to be pre-released after the call * Full release expected this week after the testing is completed * Accompanying DBSync version (13.7.0.5?) doesnt need additional integration * Readiness tracker was updated jointly on the call, increasing percentage readiness for few units * Missing ownership on readiness items addressed * There was a poll Assuming 11.0.1 is released as a pre-release version, do you agree to submit van Rossem hf initiation governance action on cardano preview today, 5th May 2026? where majority of hfwg members voted in favor of submitting hard fork initiation governance action on preview today * There was also a real concern shared that the tools might not have enough time to upgrade the node version to 11.0.1 * Although integration could have happened and be valid against 10.7.1 (as no interface was expected to change), in order to "survive" the hard fork, the tools and other stakeholders need to replace 10.7.1 with 11.0.1 as soon as its released * This weeks comms are being executed and are properly handled/adjusted according to the adopted van Rossem comms plan * Risk log was updated * PreProd Plutus cost model submission is expected to be ratified by Technical Steering Committee on their meeting on Wednesday, 6th May * 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) * [van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1) * [van Rossem readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true) #### **Action items and next steps** * **Ian Hartwell:** Propagate the need to upgrade to node version 11.0.1 as its needed to "survive" the hard fork * **Samuel Leathers, John Lotoski, Kevin Hammond, Bosko Majdanac:** Hold off the action to vote on the hard fork preview governance action until evening, to assess whether to give one additional day for major tooling to upgrade in a timely manner * **TSC:** Should have a vote on 6th May on the weekly TSC meeting on submitting Plutus Cost Model governance action to PreProd * **Ryan Williams:** Explore the possibility to use CF api for exchanges to fill in status to the readiness tracker automatically * **HFWG:** Each working group member should like and repost comms posts, blogs related to van Rossem and reported to the working group channel * **Bosko Majdanac:** Create incident RACI for van Rossem so it reflects and complements the role of the Security Council --- # 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/5th-may-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.