> For the complete documentation index, see [llms.txt](https://cardanoupgrades.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/4th-august-2026.md).

# 4th August 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/overview/hard-fork-working-group-meeting-minutes/30th-july-2026#action-items-and-next-steps) - Bosko
2. [Dijkstra era hard fork](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era/dijkstra-overview) - Bosko, all
   1. Scope
      1. IO Team presented their plan
      2. [Product committee - Dijkstra Era: Phased Rollout Plan](https://product.cardano.intersectmbo.org/hardfork-planning/dijkstra/)
   2. Node diversity
      1. Haskell, Amaru (Rust), Dingo (Go), Dugite (Rust), TSUNAGI (Zig), Gerolamo (TypeScript), Dolos (Rust), Turbocardano (C++), Razor (.NET), Scalus (Scala)
3. AOB

#### Key materials

* Summary
  * **Dijkstra Era hard fork**
    * Scope
      * Scope stays the one presented by IO Haskell node team and is available [here](https://product.cardano.intersectmbo.org/hardfork-planning/dijkstra/)
      * [**Dijkstra Era: Phased Rollout plan**](https://product.cardano.intersectmbo.org/hardfork-planning/dijkstra/) will be moved to [Cardano Upgrades space](https://cardanoupgrades.docs.intersectmbo.org/)
    * Timing
      * The rollout plan is split into two phases, one being completed in Q4 2026, the other one in Q2 2027
    * Node Diversity
      * Michael from Dugite node team was present at the meeting and gave a quick brief on the Dugite node itself
  * Hard Fork Working Group will continue to meet once a week starting this week, now that the  Dijkstra era hard fork scope is setlast week
* Hard Fork Working Group communication channels
  * [Discord](https://discord.com/channels/1136727663583698984/1242097284619960411) — `#wg-hard-fork`
  * [Weekly bulletins](https://x.com/IntersectMBO)
  * [Luma calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif)
  * [Email](mailto:hard-fork@intersectmbo.org)
* [Product committee - Dijkstra Era: Phased Rollout Plan](https://product.cardano.intersectmbo.org/hardfork-planning/dijkstra/)
* [Recording](https://drive.google.com/file/d/12qmvxQrrfQKq88XBh-S4x5YnfN7EeMau/view?usp=drive_link)
* [Transcript](https://docs.google.com/document/d/1PxX-n2FkZ7W7_nb6M7VNGnUzDxGZ1FfxbekJC4pzUtE/edit?usp=drive_link)
* [Chat](https://drive.google.com/file/d/1FmNTk6PtZ_DyGN-RzQ7CuX3P9qAzt_Gt/view?usp=drive_link)

#### **Action items and next steps**

* **Bosko:** [**Dijkstra Era: Phased Rollout plan**](https://product.cardano.intersectmbo.org/hardfork-planning/dijkstra/) should be moved to [Cardano Upgrades space](https://cardanoupgrades.docs.intersectmbo.org/)
* **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)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/4th-august-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.