16th June 2026

Agenda

1. Action items from the last call - Bosko

   1. from the Go/No-go call on 15th June: van Rossem upgrade FAQ should be expanded to include precise information breakdown based on the prepared van Rossem hard fork metadata

2. Node 11.0.1 & DBSync 13.7.1.0 - Sam

   1. IO have released Docker version of the Ogmios and Kupo

   2. Cardano Marketplace Benchmarks done by DQuadrant team - Bosko Node 11.0.1 vs 10.1.2

      • "The overall result is encouraging: marketplace transactions execute with lower Plutus resource usage, while reference-script costs now better reflect their impact on the network."

3. Van Rossem Upgrade Update - Bosko, all

   1. PoolTool

      1. Nodes reporting 11.0.1 - 62% ↑ (+8)

      2. Blocks Protocol Version current epoch - 81% ↑ (+5)

   2. Cexplorer HF readiness

      1. Block production v11 last 5 days ~ 88% ↑ (+3)

   3. Readiness tracker

4. van Rossem hard fork progress - Bosko

   1. Mainnet governance action - expected to be submitted today, epoch 637

      1. Possible Ratification Dates

         • June 23rd, June 28th, July 3rd, July 8th, July 13th, July 18th

      2. Possible Enactment Dates

         • June 28th, July 3rd, July 8th, July 13th, July 18th, July 23rd

5. Plutus Cost Model - Kevin, Ryan, Bosko

   1. Mainnet - ratified on 13th June, will be enacted 18th June

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 - Bosko

8. Technical support before and after hard fork enactment - Bosko

9. AOB

Key materials

• Summary

  • IO have released Docker version of the Ogmios and Kupo

  • Hard fork initiation governance action is expected to be submitted to mainnet soon

  • Hard fork working group should be ready to receive any and respond to any question accordingly

    • It should especially put effort into helping all voting groups: DReps, SPOs and CC members to understand changes being introduced with this intra-era hard fork

    • Hard fork working group will not put any voter group under pressure to vote

      • It will instead increase and elevate communication while remaining available to clarify any feedback or questions coming out of the feedback loop

  • Risk log have been adjusted accordingly with several items being downgraded on likelihood aspect

  • Tech support process and adjacent resource tracker have been drafted and shared

    • They need to be finalized in order to become operational (include IO, CF and Intersect)

• Hard Fork Working Group communication channels

  • Discord — #wg-hard-fork

  • Weekly bulletins

  • Luma calendar

  • Email

• van Rossem Upgrade Update

• van Rossem readiness tracker

Action items and next steps

• Larisa/Ian/Bosko: Help all voting groups: DReps, SPOs and CC members to understand changes being introduced with this intra-era hard fork and document it in the Cardano Upgrades GitBook space

• Bosko: Tech support process and adjacent resource tracker need to be finalized in order to become operational (include IO, CF and Intersect)