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

# 16th June 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/11th-june-2026#action-items-and-next-steps) - Bosko
   1. **from the Go/No-go call on 15th June:** [van Rossem upgrade FAQ](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/van-rossem-upgrade-faq) should be expanded to include precise information breakdown based on the prepared van Rossem hard fork metadata
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. IO have released Docker version of the [Ogmios](https://github.com/IntersectMBO/ogmios/) and [Kupo](https://github.com/IntersectMBO/kupo/)
   2. Cardano Marketplace Benchmarks done by DQuadrant team - Bosko\
      [Node 11.0.1 vs 10.1.2](https://docs.google.com/document/d/11hVMlOvB8gaVE8EmLvHAblWgQ6PkcXwXkKROauV1M7Q/edit?usp=sharing)
      * *"The overall result is encouraging: marketplace transactions execute with lower Plutus resource usage, while reference-script costs now better reflect their impact on the network."*
3. [Van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1) - Bosko, all
   1. [PoolTool](https://pooltool.io/networkhealth)
      1. Nodes reporting 11.0.1 - 62% <mark style="color:green;">**↑ (+8)**</mark>
      2. Blocks Protocol Version current epoch - 81% <mark style="color:green;">**↑ (+5)**</mark>
   2. [Cexplorer HF readiness](https://cexplorer.io/hardfork?block=5_days)
      1. Block production v11 last 5 days \~ 88% <mark style="color:green;">**↑ (+3)**</mark>
   3. [Readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?usp=sharing\&ouid=106134819668558877362\&rtpof=true\&sd=true)
4. van Rossem hard fork progress - Bosko
   1. Mainnet governance action - expected to be submitted today, **epoch 637**
      1. Possible Ratification Dates
         * June 23rd, June 28th, July 3rd, July 8th, July 13th, July 18th
      2. Possible Enactment Dates
         * June 28th, July 3rd, July 8th, July 13th, July 18th, July 23rd
5. Plutus Cost Model - Kevin, Ryan, Bosko
   1. [Mainnet](https://adastat.net/governances/c82f3834898e4d70d3605fa0d92ffe31345701075b107a54309c1525f9581f6200) - ratified on **13th June**, will be enacted **18th June**
6. 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
7. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724) - Bosko
8. Technical support before and after hard fork enactment - Bosko
9. AOB

#### Key materials

* Summary
  * IO have released Docker version of the [Ogmios](https://github.com/IntersectMBO/ogmios/) and [Kupo](https://github.com/IntersectMBO/kupo/)
  * Hard fork initiation governance action is expected to be submitted to mainnet soon
  * Hard fork working group should be ready to receive any and respond to any question accordingly
    * It should especially put effort into helping all voting groups: DReps, SPOs and CC members to understand changes being introduced with this intra-era hard fork
    * Hard fork working group will not put any voter group under pressure to vote
      * It will instead increase and elevate communication while remaining available to clarify any feedback or questions coming out of the feedback loop
  * Risk log have been adjusted accordingly with several items being downgraded on likelihood aspect
  * Tech support process and adjacent resource tracker have been drafted and shared
    * They need to be finalized in order to become operational (include IO, CF and Intersect)
* 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**

* **Larisa/Ian/Bosko:** Help all voting groups: DReps, SPOs and CC members to understand changes being introduced with this intra-era hard fork and document it in the Cardano Upgrades GitBook space
* **Bosko:** Tech support process and adjacent resource tracker need to be finalized in order to become operational (include IO, CF and Intersect)


---

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