30th July 2026

Agenda

1. Action items from the last call - Bosko

2. Dijkstra era hard fork - Bosko, all

   1. Scope

      1. Product committee - Dijkstra Era: Phased Rollout Plan

   2. Node diversity

      1. Haskell, Amaru (Rust), Dingo (Go), Dugite (Rust), TSUNAGI (Zig), Gerolamo (TypeScript), Dolos (Rust), Turbocardano (C++), Razor (.NET), Scalus (Scala)

      2. Diversity is inevitable, but also are risks that come with it

         1. Bounty Evaluation for Dugite alternate node by Pi

3. AOB

Key materials

• Summary

  • Dijkstra Era hard fork

    • Scope

      • Jeff from IO attended the Technical Steering Committee meeting on 29th July to present the scope for Dijkstra and plans for delivery

        • Timelines and scope presented will be merged into the Product committee - Dijkstra Era: Phased Rollout Plan and added to Dijkstra space in the hard fork working group

        • Plutus V4 is expected to be ready in September 2026

    • Timing

      • Delivering nested transactions and linear leios (among other items from the presented scope) to mainnet by the end of 2026, remain the working goal of the Haskell node team

    • Node Diversity

      • Given already significant number of nodes of different types being at different stages of development, the working group acknowledges the risks it can bring

        • There needs to be a certification process and gating for block producing nodes in order to become part of the public networks and be widely endorsed. Thats something that Intersect can help define

        • Example analysis: Bounty Evaluation for Dugite alternate node by Pi

      • Haskell node team is exploring possibilities of exposing benchmarking and regression testing to other node teams

      • In light to the above, representatives from all alternative node teams have been invited to the hard fork working group meeting in order to align, coordinate and bring improvements to the Cardano ecosystem together

  • Hard Fork Working Group will reduce the number of meetings to once a week, starting from next week, after the Dijkstra era hard fork scope is expected to be set by the end of this week

• Hard Fork Working Group communication channels

  • Discord — #wg-hard-fork

  • Weekly bulletins

  • Luma calendar

  • Email

• Product committee - Dijkstra Era: Phased Rollout Plan

• Recording

• Transcript

• Chat

Action items and next steps

• Bosko: Reduce the frequency of Hard Fork working group meetings to once a week

• Carlos: Attend the next parameter committee call in 2 weeks to further discuss the impact on constitution and parameters for the Dijkstra era hard fork

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