12th May 2026

Agenda

1. Action items from the last call - Bosko

2. Node 11.0.1 & DBSync 13.7.0.5 - Sam/Ramsay/Jeff

3. Van Rossem Upgrade Update - Bosko, all

   1. Readiness tracker

4. van Rossem hard fork on Cardano networks - Bosko

   1. Preview - forked on 8th May

   2. PreProd

      1. Cardanoscan

      2. Cexplorer

      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)

   3. Mainnet

      1. Are we on the track to submit it on 29th May?

5. Plutus Cost Model on Cardano Networks - Ryan, Kevin, Bosko

   1. Preview - submitted, ratified and enacted

   2. PreProd - submitted and ratified, will be enacted at epoch boundary on 16th May

   3. Mainnet

      1. Are we ready to submit the governance action to mainnet this week?

6. van Rossem comms - Ian / Larisa

   1. Comms in the last week - anything we missed

   2. Comms in the week ahead

7. Risk log

8. AOB

Key materials

• Summary

  • Node 11.0.1 & DBSync 13.7.0.5, although fully ready and released, will be left on the agenda as a standing item should any issue with them occur during the testing, integration and adoption phase

  • Readiness tracker is updated with the lastest information so the readiness number is now more realistic and sits around 46%

  • van Rossem hard fork on Cardano networks

    • Still waiting on Ogmios readiness update to be able to decide on voting, ratification and enactment of the van Rossem hard fork on PreProd

      • first possible enactment date is 21st May if its voted for until 16th May - epoch boundary on PreProd

    • Mainnet hf ga submission date still stands for 29th May

  • Plutus Cost Model on Cardano Networks

    • PreProd - submitted and ratified, will be enacted at epoch boundary on 16th May

    • Plutus cost model is expected to be submitted on mainnet this week, pending TSC ratification on the meeting tomorrow afternoon, 13th May

  • van Rossem comms - It was emphasized that the van Rossem hf comms landscape is ever changing with more things to be added and a need for them to be communicated widely

    • risk around hf comms has increased likelihood from (L)ow to (M)edium with an expressed need to involve senior community stakeholders that can help spread the message in the right way (expectations management)

• 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

• Ian, Larisa: Involve senior community stakeholders in helping spread the right message, to explain to SPOs why does the roadmap to van Rossem have particular look/shape and why certain things are done the way they are done

• 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

• HFWG: Each working group member should like and repost comms posts, blogs related to van Rossem and reported to the working group channel