7th May 2026

Agenda

1. Action items from the last call - Bosko

2. Node 11.0.1 - Sam/Ramsay/Jeff

   1. DBSync 13.7.0.5

3. van Rossem on Preview

   1. Govtool

   2. Cardanoscan

   3. Cexplorer

4. Van Rossem Upgrade Update - Bosko, all

   1. Readiness tracker

5. van Rossem comms - Ian / Larisa

   1. Key dates and events for van Rossem upgrade - April, May, June 2026

6. Risk log

7. Incident RACI (van Rossem) - Bosko

8. Plutus Cost Model - Ryan

9. AOB

Key materials

• Summary

  • Node version 11.0.1 has been released today

    • This is the node version capable of "surviving" hard fork

  • Accompanying DBSync version 13.7.0.5 has also been released today

  • Cardano Preview Testnet is expected to fork 8th May on an epoch boundary

  • Readiness was assessed through different ecosystem aspect and the biggest identified risk is potential delay of Ogmios readiness which is added to the risk log

  • Hard Fork Working Group decided unanimously that the hard fork initiation governance action should be submitted today or tomorrow and will be then assessed by the Hard Fork Working Group itself for voting, ratification and enactment effort pending Ogmios readiness risk mitigation

  • van Rossem comms are executed based on this weeks plan with a couple of additional inputs like node 11.0.1 and dbsync 13.7.0.5 being released, preprod plutus cost models governance action submitted and hard fork initiation governance action soon to be submitted

• Hard Fork Working Group communication channels

  • Discord — #wg-hard-fork

  • Weekly bulletins

  • Luma calendar

• van Rossem Upgrade Update

• van Rossem readiness tracker

Action items and next steps

• Ryan Williams, Leonard, Kevin, Michiel, Bosko: Have a call to assess Ogmios readiness risk mitigation

• Bosko: Have an initial call with IO and Intersect people on drafted van Rossem support RACI matrix

• Leonard, Ryan Williams, Bosko: Assess the list of dApps that benefit from the new Plutus primitives

• 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