2nd July 2026

Agenda

1. Action items from the last call - Bosko

2. Node 11.0.1 & DBSync 13.7.1.0 - Sam

   1. Cardano Solutions/Ogmios - Ready

   2. Kupo (Intersect forked version)

3. Van Rossem Upgrade Update - Bosko, all

   1. PoolTool - Blocks Protocol Version current epoch - 88%

   2. Cexplorer HF readiness - Block production v11 last 5 days ~94%

   3. Cardanoscan Exchanges - Liquidity Ready 80.19%

   4. Hard Fork ratification readiness - tracker

4. van Rossem hard fork progress - Bosko

   1. Mainnet governance action

      1. Possible Ratification Dates

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

      2. Possible Enactment Dates

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

5. van Rossem comms - Ian / Larisa

   1. Comms in the last week - anything we missed

   2. Comms in the week ahead

6. Risk log - Bosko

7. Technical support before and after hard fork enactment - Bosko, Can

8. Dijkstra era hard fork

9. AOB

Key materials

• Summary

  • According to PoolTool, blocks Protocol Version current epoch at 89%

  • According to CExplorer, block production v11 last 5 days is at ~94%

  • Hard Fork initiation governance action current support

    • DReps at 66.60%

    • SPOs at 43.21%

    • CC at 14% (1 vote out of 5 needed)

  • Next epoch boundary is very unlikely to be the ratification date with higher probability to happen on Wednesday, 8th July

  • All ratification metrics have been met

  • Comms and messaging is and will be focused on SPOs and CC giving them all the relevant data, tracker points and readiness state to consider it for voting

  • Risk log has been further adjusted with closing some risk items

  • On call document for the period before and after enactment of the van Rossem governance action has further been populated

  • Starting next week, Thursdays hard fork working group meeting will be more focused on next hard fork in Dijkstra era

• 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

• Ian/Larisa: Comms and messaging should include and be focused on SPOs and CC giving them all the relevant data, tracker points and readiness state to consider it for voting

• Bosko: Repurpose Thursdays hard fork working group meetings to have more focus on Dijkstra era hard fork