> 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/25th-june-2026.md).

# 25th June 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/23rd-june-2026#action-items-and-next-steps) - Matt
2. [Node 11.0.1](https://github.com/IntersectMBO/cardano-node/releases/tag/11.0.1) & [DBSync 13.7.1.0](https://github.com/IntersectMBO/cardano-db-sync/releases/tag/13.7.1.0) - Sam
   1. [Cardano Solutions/Ogmios](https://github.com/CardanoSolutions/ogmios/releases/tag/v7.0.0) - <mark style="color:green;">**Ready ↑**</mark>
   2. [Kupo](https://github.com/IntersectMBO/kupo/) (Intersect forked version)&#x20;
3. [Van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1) - Matt, all
   1. [PoolTool](https://pooltool.io/networkhealth)
      1. Nodes reporting 11.0.1 - 91% <mark style="color:green;">**(+0)**</mark>
      2. Blocks Protocol Version current epoch - 87% <mark style="color:green;">**↑ (+1)**</mark>
   2. [Cexplorer HF readiness](https://cexplorer.io/hardfork?block=5_days)
      1. Block production v11 last 5 days \~ 91.4% <mark style="color:green;">**↑ (+1)**</mark>
   3. [Cardanoscan Exchanges](https://cardanoscan.io/hfReadiness)
      1. 23 - Ready, 12 - In Progress
      2. Liquidity Ready 67.6% ↑ <mark style="color:green;">**(+17)**</mark>
   4. [Readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true)
4. van Rossem hard fork progress - Matt
   1. Mainnet governance action
      1. Possible Ratification Dates
         * June 28th, July 3rd, July 8th, July 13th, July 18th
      2. Possible Enactment Dates
         * July 3rd, July 8th, July 13th, July 18th, July 23rd
5. van Rossem comms - Ian / Larisa
   1. Comms plan - CF, Midnight, Shielded, Emurgo, Intersect, IO
      1. Weekly comms meeting
   2. Comms in the last week - anything we missed
   3. Comms in the week ahead
6. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724) - Matt
7. Technical support before and after hard fork enactment - Matt
8. AOB

#### Key materials

* Summary
  \*
* 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)
* [van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1)
* [van Rossem readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true)

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

*


---

# 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/25th-june-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.