21st July 2026

Agenda

1. Action items from the last call - Bosko

2. Van Rossem Upgrade Update - Bosko, all

   1. Enacted on 18th July with ~10 mins gap before the first block

   2. Comms - Ian / Larisa

   3. Technical support before and after hard fork enactment - Can

      1. Risk log

3. Dijkstra era hard fork - Bosko, all

   1. Scope

      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

    • SRE team and engineering teams are on standby for at least one epoch to observe whether there will be any issue similar to what happened on the van Rossem enactment epoch boundary

  • Dijkstra Era hard fork

    • Scope

      • In addition to the scope candidates presented last week on the hfwg call, few additional CIP were discussed and assessed

        • CIP-151 is still being discussed as a CIP so its not likely to fit into the first next hard fork in Dijkstra era

          • Since it needs full era, it would likely end up in era after Dijkstra, so Euler

        • CIP-181 has reasonable chances to be included

        • CIP-50 might be added to the scope by external contributor

          • Ryan (Cerkoryn) Wiley is leading that effort and wil reach out to the Haskell team on potential integration

      • Discussed scope will be presented to both Product Committee and Technical Steering Committee meetings on Wednesday, 22nd July

    • Timing

      • Q4 2026 remains the working target for DIjkstra era hard fork

    • Prioritization & process

      • Work is continuing so there is a meaningful and impactful process for community participation in defining the scope of any future hard forks post first one in Dijkstra era

    • Next hard fork naming

      • There was a number of prominent community members mentioned who passed away recently

      • CIP-179 can potentially be used for multi-option voting through info action

      • This topic will be on agenda for the next hard fork working group meeting this week, on Thursday, 23rd July

  • 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

• Recording

• Transcript

• Chat

Action items and next steps

• Can/Sam: Make sure that SRE and engineering teams observe network behavior for block propagation delay as it happened on van Rossem hard fork enactment on the next epoch boundary on Thursday, 23rd July

• Ryan (Cerkoryn): Reach out to Haskell team (Geoff/Brandon) to check on the posibility of integration of CIP-50 done by external contributor

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