> 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/18th-june-2026.md).
# 18th June 2026
#### Agenda
1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/16th-june-2026#action-items-and-next-steps) - Bosko
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. [Ogmios](https://github.com/IntersectMBO/ogmios/) and [Kupo](https://github.com/IntersectMBO/kupo/)
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 - 63% **↑ (+1)**
2. Blocks Protocol Version current epoch - 81%
2. [Cexplorer HF readiness](https://cexplorer.io/hardfork?block=5_days)
1. Block production v11 last 5 days \~ 89% **↑ (+1)**
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 - submitted on **16th June**, **epoch 637**
1. [Adastat](https://adastat.net/governances/fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d00)
2. [Cexplorer](https://cexplorer.io/gov/action/fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d%25230)
3. [Cardanoscan](https://cardanoscan.io/govAction/gov_action1lh2x3kjucjkggvwu6l3txggkvmrnhs3flpv8j35lvlcan4gax3xsq3cxfjc)
4. [GovTool](https://gov.tools/governance_actions/fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d#0)
5. None of the tools are showing the SPO percentages correctly - for the HF type of governance actions, **auto-abstain is counted as no**
2. Possible Ratification Dates
* June 23rd, June 28th, July 3rd, July 8th, July 13th, July 18th
3. 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 later **today**, on the epoch boundary
6. MinCommitteeSize 7 to 5 - Kevin, Ryan, Bosko
1. Currently at \~30.75%
7. 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
8. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724) - Bosko
9. Technical support before and after hard fork enactment - Bosko
10. AOB
#### Key materials
* Summary
* Forked Ogmios and Kupo should continue to be used for ecosystem integration and readiness until the original Ogmios and Kupo repos are updated and made van Rossem compatible (expected next week)
* Pools continue to adopt node version 11.0.1 with more than 80% blocks in the current epoch produced with protocol v11
* This is above the "would like to see" 80% for the hard fork governance action ratification
* More exchanges are becoming ready with 36.8% currently ready
* 44.46% of exchanges based on their liquidity are in progress and once those become ready, it will go above the "would like to see" 80% for the hard fork governance action ratification
* Dapps readiness, currently at \~70%, is close to the threshold of the "would like to see" 80% for the hard fork governance action ratification
* Plutus Cost Model governance action will be enacted later today at the epoch boundary
* MinCommitteeSize governance action currently sits at \~31% of support with 20 days left for it to pass the 67% DRep support threshold
* van Rossem comms team has a strong grip on making updates publicly available to all ada holders and stakeholders
* The team is consistently executing on comms plan and is ready to purse different paths if it becomes needed
* Risk log items have been further downgraded with some of them being closed
* Technical support before and after enactment of the hard fork governance action remains in focus of the hard fork working group and all Cardano entities (IO, Cardano Foundation, Emurgo, Midnight and Intersect) with the resourcing plan being adjusted in order to secure timely reactions and consistent feedback loops
* 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**
* **Bosko:** Add Ogmios and Kupo original codebases progress is a standing agenda item in the next hard fork working group meetings
* **Larisa/Ian:** Include explanation of how pools auto-abstains are counted in the case of the hard fork type of governance action
---
# 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/18th-june-2026.md?ask=&goal=
```
`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.