> 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/19th-may-2026.md).
# 19th May 2026
#### Agenda
1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/14th-may-2026#action-items-and-next-steps) - Bosko
2. [Node 11.0.1](https://github.com/IntersectMBO/cardano-node/releases/tag/11.0.1) & [DBSync 13.7.0.5](https://github.com/IntersectMBO/cardano-db-sync/releases/tag/13.7.0.5) - 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. Ogmios [PR](https://github.com/CardanoSolutions/ogmios/pull/461)
1. Can it be done so its van Rossem ready instead of Dijkstra ready?
2. How would Dijkstra features be enabled later?
2. Kupo [PR #1](https://github.com/CardanoSolutions/kupo/pull/203) & [PR#2](https://github.com/CardanoSolutions/kupo/pull/204)
1. Potential alternative path to progress without explicit need for Ogmios? - Sam
3. [Readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true)
4. van Rossem hard fork progress - Bosko
1. PreProd
1. [Cardanoscan](https://preprod.cardanoscan.io/govAction/gov_action108a5htqnmlp89ffn2ucf7u9u33s0r9gpx7eytpdc2q28y50ly42qqf9jcen)
2. [Cexplorer](https://preprod.cexplorer.io/gov/action/79fb4bac13dfc272a53357309f70bc8c60f1950137b24585b850147251ff2554%25230)
3. Are we ready to vote, ratify and enact hf ga on preprod? (first next possible enactment date is **26st May** if its voted for until **21st May** - epoch boundary on PreProd)
2. Mainnet
1. Are we on the track to submit it on **29th May**?
5. Plutus Cost Model - Kevin, Ryan, Bosko
1. PreProd - submitted, ratified, was enacted at the epoch boundary on **16th May**
2. Mainnet
6. van Rossem comms - Ian / Larisa
1. Comms plan - CF, Midnight, Shielded, Emurgo, Intersect, IO
1. Weekly comms meeting
2. Comms in the last week - anything we missed
3. Comms in the week ahead
7. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724)
8. AOB
#### Key materials
* Summary
* Ogmios and Kupo readiness continues to be the biggest challenge for the hard fork progress
* Ogmios should be added to the critical tooling list
* It should be pointed out in any comms mentioning that Ogmios isnt ready yet, that its the private project
* Main issue from the Ogmios team perspective is that the impact is big due to the fact that the node version 11.0.1, which is meant for van Rossem, also contains some feature of the future hard fork/era Dijkstra
* IO team members John and Erik created massive PRs in draft trying to unblock progress even though its not their codebase
* Matthias from the Ogmios team is participating as much as possible giving his guidance, reviews and technical expertise but time availability continues to be the issue
* There are at least two possible approaches
* Continue to work on the PRs in their current state trying to get them over the line and in the position to be merged or
* Create PRs with the reduced scope to focus on the van Rossem readiness support and keeing Dijkstra features support as little as needed
* It was decided that IO team should try to get additional resources in reviewing the work being done by John and Erik and giving it potentially the last needed push
* There needs to be a rapid progress made in less than 2 days, before the next hard fork working group meeting on 21st May (which is also a preprod epoch boundary)
* That is supposed to be the last possible date when the hard fork working group can recommend forking Cardano PreProd testnet (governance action ratification would be enacted on 21st and enacted 5 days later on 26th of May). The governance action submission date for mainnet would stay the same, **29th May**.
* The criteria is relatively simple, Ogmios PRs is raised and official
* If there is no Ogmios PR raised before the next PreProd epoch boundary on 21st, hard fork is highly likely to be delayed by at least one epoch, possibly more (depends on the iterative development work being done on the PR itself)
* Exchanges need Rosetta-Java (expected by the end of next week) to be ready in order to progress on readiness, and Rosetta-Java is dependent on Yaci Store which is expected to become ready by the end of this week
* All exchanges have been contacted
* Overall readiness steadily increases
* More ecosystem tooling becomes ready each day
* SPO adoption rate of the hard fork ready node 11.0.1 is growing and is now at 32% according to pooltool.io (more than 10% increase in the last 5 days). This sets it as the version with the biggest single share.
* Cardano entities (IO, Cardano Foundation, Midnight, Emurgo and Intersect) have established comms weeklies on Monday and also agreed communication channels for better collaboration and propagation of van Rossem related comms
* Risk log was updated with increased likelihood for `Community is not ready for the Hard Fork`, `Failure to Hard Fork in a Timely Manner` and `Ogmios upgrade not ready` risks
* 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**
* **Sam/Ramsay/Kevin/Bosko:** Have a discussion with the IO developer teams in the release meeting later today to check whether anybody can pick up the remianing work on Ogmios PR and do it rapidly so PreProd hard fork governance action can be ratified on 21st and enacted on 26th. That allows the possibility of still submitting mainnet hard fork governance action on 29th
* **Sam:** Inform IO execs of the potential hard fork delay
* **Bosko:** Inform Intersect execs of the potential hard fork delay
* **Bosko/Sam/Kevin:** Make sure Ogmios is added to the critical tooling list
* **Bosko:** Have an initial call with IO and Intersect people on drafted van Rossem support RACI matrix
---
# 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/19th-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.