16th July 2026

Agenda

1. Action items from the last call - Bosko

2. Van Rossem Upgrade Update - Bosko, all

   1. Ratified on 13th July, will be enacted on 18th July

   2. ~94-96% blocks with protocol v11 produced, exchanges at 84.19% readiness

   3. Risk log

   4. Comms - Ian / Larisa

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

3. Dijkstra era hard fork - Bosko, all

   1. Walkthrough of the scope being worked against by the Haskell node team(s) - Geoff/Carlos/Alexey/Sam

      1. Product committee - Initial Dijkstra scope

   2. CIP 179 - Tesera application - Matthieu P, Thomas L, Ryan C

      1. Repo

      2. Context on what now + potential future PR

4. AOB

Key materials

• Summary

  • van Rossem hard fork

    • Ratified on 13th July (643), will be enacted on 18th July (644)

    • van Rossem public call has been scheduled

      • Saturday, 18th July, 9:15pm UTC

  • Dijkstra Era hard fork

    • Scope

      • Haskell node team gave the walkthrough of the scope they are working against

      • Leios and nested transactions are key drivers of the next Dijkstra ready, haskell node release

      • CIP-159 is prerequisite for multi asset treasury

      • CIP-23 will likely be added to the scope

      • The goal for Peras is to be enabled in full era and activated in intra era hard fork

    • Timing

      • The goal for Dijkstra era hard fork is to be enacted by the end of 2026

    • Prioritization & process

      • Drafting and structuring of the process that will enable prioritization and scope decision making for the hard fork after Dijkstra is under way as agreed on the last hard fork working group call

    • Anticipated challenges

      • Due to the changes that Leios brings, exchanges will need to change their operational procedures so its advised to include exchanges in testing as soon as the upcoming changes are merged into the codebase

  • Hard Fork Working Group meetings will continue to happen twice a week, until at least the Dijkstra hard fork scope is set, after which the future meeting cadence will be decided

• Hard Fork Working Group communication channels

  • Discord — #wg-hard-fork

  • Weekly bulletins

  • Luma calendar

  • Email

• van Rossem readiness tracker

• Recording

• Transcript

• Chat

Action items and next steps

• Geoff: Attend the Technical Steering Committee meeting on 29th July to present the scope for Dijkstra and plans for delivery

• Kevin/Sam L/Ryan C W: Draft the decision making and prioritization process for future hard forks

• Bosko: Continue creating supporting structure and relevant documentation within the hard fork working group GitBook space under Technical Steering Committee

• Tex: Create ecosystem dependency mapping document(s)