> 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-may-2026.md).

# 14th May 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/12th-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)
   2. Kupo [PR #1](https://github.com/CardanoSolutions/kupo/pull/203) & [PR#2](https://github.com/CardanoSolutions/kupo/pull/204)
   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 possible enactment date is **21st May** if its voted for until **16th 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 and ratified, will be enacted at epoch boundary on **16th May**
   2. Mainnet
6. van Rossem comms - Ian / Larisa
   1. Comms plan - CF, Midnight, Shielded, Emurgo, Intersect, IO
      1. Slack channel created
      2. Weekly comms meeting scheduled
   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
  * Hard Fork Working Group decided to not recommend forking the Cardano PreProd network until there are merged PRs that are addressing Ogmios and Kupo hard fork readiness which can happen in the next few days
    * Likely, the first possible hard fork enactment date on PreProd becomes 26th May (assuming it would be ratified on the previous epoch boundary on 21st May)
  * The above will be included in the comms plan to be executed in the following days
* 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, Larisa:** Include in the comms plan and communicate the Ogmios and Kupo challenges to the wider community reassuring them PRs are being worked on and are coming soon
* **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/14th-may-2026.md?ask=<question>&goal=<endgoal>
```

`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.