> 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/17th-november-2026.md).

# 17th November 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/10th-november-2026#action-items-and-next-steps) - Bosko
2. [Dijkstra era hard fork](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era/dijkstra-overview) - Bosko, all
   1. Releases
      1. 11.2.1, 11.2.2, 11.2.3 - Jeff, Amani, Sam
      2. 11.3 - Sebastian
      3. [Project view of versions](https://github.com/orgs/input-output-hk/projects/167/views/15)
   2. [Dijkstra risk log](https://docs.google.com/spreadsheets/d/1NXMFkCpqNlq8SPSgzPNi_ZYLUg25tVWU-i4yz7fQhcI/edit?gid=66373110#gid=66373110) review
   3. Scope
      1. Each remaining scope item (besides CIP-23 and CIP-50 which are already documented) have its impact documented ([PR](https://github.com/IntersectMBO/hf-wg-documentation/pull/43) opened) in the [Cardano Upgrades space](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-overview) (Core semantics changes, Breaking API changes, New features)
         * [Updated Leios impact assessment available for feedback](https://drive.google.com/file/d/1GJNMixEGb6-jEOh8Yy_p2N--cPPz1Jh6/view?usp=sharing) (passed from TSC to original authors)
   4. Constitutional amendments - [Dijkstra era parameters in CAP](https://cap.intersectmbo.org/#/detail/12)
   5. Comms - Larisa, Ian, Matthew
   6. Node diversity
      1. [Blocks produced on mainnet](https://kleioscan.com/#/mainnet/nodes)
         * cardano-node, Amaru, Dingo, cardano-bean, tsunagi
      2. Node diversity workshop in London last week, **12th&13th November** organized by Amaru team
         * [Node diversity - Building cost efficient software the "Cardano Way"](https://x.com/Amaru_Cardano/status/2122473330758586462?a=aftT0hlT6IQUlSGlVYQ\&s=20)
         * [X post](https://x.com/Amaru_Cardano/status/2122473569191948308?a=hz1EpdGAiEVnZXmJvWQ\&s=20)
      3. Haskell, Amaru (Rust), Dingo (Go), Dugite (Rust), TSUNAGI (Zig), Gerolamo (TypeScript), Dolos (Rust), Turbocardano (C++), Razor (.NET), Scalus (Scala), Yano (Java)
3. Hard Fork Working Group funding (Technical Steering Committee budget)
   1. Application form - <https://forms.clickup.com/9015279944/f/8cnmga8-55475/D8A3VU9CZOQQU56CYX>
4. AOB

#### Key materials

* Summary
  * **Dijkstra Era hard fork**
    * Releases
      * 11.2.1, 11.2.2, 11.2.3
        * 11.2.1 is the last pre-released version and is used to run DijkstraNet at the moment
        * 11.2.2 was delayed a bit due to the conformance issue discovered at the Node diversity workshop, fix is expected soon (tag is available [here](https://github.com/IntersectMBO/cardano-node/releases/tag/11.2.2))
          * Regression testing was done and proved version reached good quality
        * 11.2.3, that will address conformance issue fix, is expected to be pre-released soon and made mainnet ready by the end of this week
        * These versions are not capable of surviving the hard fork
      * [11.3](https://github.com/orgs/input-output-hk/projects/167/views/15)
        * Main stream of work at the moment relates to review of \~10000 lines of code
        * Smaller "plumbing" things expected to be finalized
        * It is expected to be pre-released in 2-3 weeks after which DijkstraNet will be re-forked
        * This is the first candidate that has a chance to be promoted to 12.0 provided successful testing without any showstopper issues
        * DBSync version is being developed in parallel with the Leios progress and it will become available shortly after 11.3 has been released
    * Cardano Testnets
      * DijkstraNet
        * Currently running with the pre-released 11.2.1 version of the node
          * It includes all of the Dijkstra scope but Linear Leios (CIP-164) and Fair Min Fees (CIP-23)
          * It also allows registration of BLS keys
        * Downstream tooling teams are encouraged to start the integration against the available Dijkstra era feature set
        * Advanced configuration of DijkstraNet Testnet available [here](https://book.play.dev.cardano.org/adv-dijkstra.html)
        * Discord channel: [dijkstra-net](https://discord.com/channels/826816523368005654/1565517149047361586)
      * Musashi Testnet
        * Downstream tooling teams are encouraged to do the early integration against 11.3 prototype on Musashi Testnet
        * Week 46 node release available [here](https://github.com/input-output-hk/ouroboros-leios/releases/tag/rc-2026w46)
        * Discord channel: [musashi-testnet](https://discord.com/channels/826816523368005654/1517210858365911242)
      * SanchoNet
        * Expected to soon fork into the Dijkstra era
        * Discord channel: [sanchonet](https://discord.com/channels/826816523368005654/1141734250438197370)
      * Preview
        * The goal is to fork Preview testnet to Dijkstra era before the holidays given the right conditions are met
          * It should be preceeded with the new constitution and guardrails governance action
        * Need to be well coordinated to respect Midnight needs
    * Scope
      * Adjusted CIP-23 impact assessment page the [Dijkstra upgrade overview](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-overview) GitBook space based on the plan for the full CIP-23 implementation in Dijkstra era
      * Merge the remaining impact assessments to the Dijkstra era GitBook space after addressing their pending reviews
    * Constitutional amendments
      * New constitution and guardrails v6 is expected [to be provided in CAP portal soon](https://cap.intersectmbo.org/#/detail/12)
        * Carlos committed to provide adjusted cost estimator
        * Security Council will look at some of the concerns with Carlos on tomorrows session
        * Background analysis should be completed before the next Parameter Committee meeting on 26th November
        * After the numbers are finalized, new guardrail script will be built and tested
        * 12.0 version of the node is ideal to finalize those, however, it could also be done with 11.3 with the slight risk
      * New constitution and guardrails governance action can either be submitted before or after the hard fork with the preference to submit it before the hard fork
        * Earliest possible date of submission would be on 25th November, beginning of epoch 670
    * Node diversity
      * [Block produced on mainnet](https://kleioscan.com/#/mainnet/nodes)
        * cardano-node, Amaru, Dingo, cardano-bean, tsunagi
      * Node diversity workshop in London last week, **12th&13th November** organized by Amaru team
        * [Node diversity - Building cost efficient software the "Cardano Way"](https://x.com/Amaru_Cardano/status/2122473330758586462?a=aftT0hlT6IQUlSGlVYQ\&s=20)
        * [X post](https://x.com/Amaru_Cardano/status/2122473569191948308?a=hz1EpdGAiEVnZXmJvWQ\&s=20)
    * Hard Fork Working Group funding (Technical Steering Committee budget)
      * [Application form](https://forms.clickup.com/9015279944/f/8cnmga8-55475/D8A3VU9CZOQQU56CYX)
    * Euler Scoping Working Group
      * Euler era which is trailing Dijkstra era has the working group formed with the early discussions on the scope
      * There is a public call scheduled for 2nd December
      * [Charter](https://docs.google.com/document/d/14YtDSJco0hqp-vWbWiNzHYkm4bOe6d9zBEPLW1k1hH0/edit?tab=t.0)
  * Hard Fork Working Group will continue to meet once a week until the Dijkstra era hard fork work solidifies enough to mandate more alignments and sync

#### **Reference links and engagement points**

* 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)
* [Dijkstra era | Cardano's next protocol upgrade](https://www.youtube.com/watch?v=k4x0eP_h1Qo)
* [BLS Key rotation](https://github.com/input-output-hk/ouroboros-leios/issues/1024)
* [Dijkstra readiness tracker](https://docs.google.com/spreadsheets/d/1C1Ai_YTqwKLHtICunzbh_o0FD9XB54Kh/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true)
* [Dijkstra Risk log](https://docs.google.com/spreadsheets/d/1NXMFkCpqNlq8SPSgzPNi_ZYLUg25tVWU-i4yz7fQhcI/edit?usp=sharing)
* [Dijkstra era parameters in CAP](https://cap.intersectmbo.org/#/detail/12)
* [Antithesis](https://cardanofoundation.org/blog/improving-cardano-antithesis)
* [Recording](https://drive.google.com/file/d/1N6rQ3Aw0r2AdeH2_VwNi0K2_TnsMJncO/view?usp=drive_link)
* [Transcript](https://docs.google.com/document/d/17rrXkxL2tWY1p2e8CPy7xpN9EgCXe6XILT-aPaxHfAE/edit?usp=drive_link)
* [Chat](https://drive.google.com/file/d/17-z5h7R0MJphPP34a6bkk8lhiKn8kzMy/view?usp=drive_link)

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

* **Leonard H/Bosko/Jeff:** Confirm the chosen path for Ogmios/Kupo from the readiness aspect
* **Carlos:** Draft the sixth version of the Cardano constitution in relation to Dijkstra era parameters
* **Carlos:** Provide updated cost estimator
* **Kevin/TSC:** Provide baseline to the Leios team for the hardware requirements
* **Bosko:** Merge the remaining impact assessments to the Dijkstra era GitBook space after addressing Kevins review of them
* **Bosko:** Adjust Dijkstra risk log for better visibility and risk management
* **Sebastian:** Adjust [project view](https://github.com/orgs/input-output-hk/projects/167/views/15) of node versions in GitHub to better reflect the remaining work
* **Bosko:** Add compatibility matrix to the [Dijkstra upgrade readiness](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-readiness) page
* **Bosko/Carlos:** Provide unified delivery timelines (high level one and more detailed one)
* **Bosko:** Inform Midnight teams of the potential to fork Cardano Preview testnet before the holiday season
* **Kevin:** Provide the link for the public call of the Euler Scoping Working Group
  * **Bosko:** Add the above link to the Hard Fork Working Group Luma calendar


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
