30th June 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

      1. Nodes reporting 11.0.1 - 91% (+0)

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

   2. Cexplorer HF readiness

      1. Block production v11 last 5 days ~93% ↑ (+2)

   3. Cardanoscan Exchanges

      1. 26 - Ready, 10 - In Progress

      2. Liquidity Ready 80.13% ↑ (+13)

   4. Readiness tracker

4. van Rossem hard fork progress - Matt

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

6. Risk log - Bosko

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

8. AOB

Key materials

• Summary

  • All ratification readiness metrics, according to the hard fork initiation submission policy, have been met with the latest ones being exchanges, passing slightly over the 80% threshold and dapps going few percentage points above 80% level

  • Based on the achieved metrics levels, hard fork working group had a vote on recommendation for van Rossem hard fork initiation governance action ratification

    • The results are, out of 17 participants:

      • Yes - 11

      • No - 0

      • Abstain 3

  • DReps ratification support is at ~65%, SPOs at ~36% and CC at 1 (out of 5 needed)

    • Delegation numbers can change at the next epoch boundary on 3rd July, thus chaning support levels, so they should be closely watched by the hard fork working group

  • Comms team will include these in the next comms pieces to help remaining voting groups who didnt yet met ratification threshold (SPOs and CC)

    • Its already putting a strong emphasis on clarification on SPOs auto-abstain meaning in the case of hard fork governance action

  • Risk log have been updated with several risks being closed as resolved

  • On-call schedule is being set for the next few weeks (covers period before and after hard fork governance action enactment

• 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: Include messaging that the SPOs can safely vote on the hard fork governance action

• Bosko/Can: Complete the on-call schedule document