> 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/11th-june-2026.md).
# 11th June 2026
#### Agenda
1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/9th-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
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. Ogmios [v6.14.0.2](https://github.com/IntersectMBO/ogmios/releases/tag/v6.14.0.2) - Jeff, Sam
2. Kupo [v2.11.0.1](https://github.com/IntersectMBO/kupo/releases/tag/v2.11.0.1) - Jeff, Sam
3. [PoolTool](https://pooltool.io/networkhealth)
1. Nodes reporting 11.0.1 - 54% **↑ (+4)**
2. Blocks Protocol Version current epoch - 76% **(0)**
4. [Cexplorer HF readiness](https://cexplorer.io/hardfork?block=5_days)
1. Block production v11 last 5 days - 85% **↑ (+1)**
5. [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. PreProd
1. Enacted on **10th June**
2. Mainnet
1. Go/No-go Mainnet hard fork initiation governance action submission date - **15th June**
2. Guardrails status
1. Technical Steering Committee approved the technical contents of the Mainnet hard fork metadata, subject to an final verification check with the IOG developers regarding completed security evaluations. ([10th June meeting reference](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/meeting-minutes/2026-tsc-meeting-minutes/meeting-minutes-june-10-2026))
2. Coordinate with the Hard Fork Working Group today to double-check the accuracy of the security verification text in the metadata - Kevin
3. Asked Civics Committee on [Discord](https://discord.com/channels/1136727663583698984/1295329867285663826/1513851728703918113)
1. Expecting feedback today - Nicolas, Larisa, Ian
3. Readiness checklist
5. Plutus Cost Model - Kevin, Ryan, Bosko
1. [Mainnet](https://adastat.net/governances/c82f3834898e4d70d3605fa0d92ffe31345701075b107a54309c1525f9581f6200) - submitted on 26th May, continuing to gain traction (currently at 55% with 17 days to go - increased 8% in the last 2 days)
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)
8. Technical support before and after hard fork enactment
9. AOB
#### Key materials
* Summary
* Ogmios and Kupo have two paths forward (both providing sufficient support to the community to progress with van Rossem hard fork readiness
* Tools author is expected to review, adjust and make van Rossem compatible versions based on the original codebase in the week of 22nd June
* Until that happens, forked versions of those tools (Ogmios [v6.14.0.2](https://github.com/IntersectMBO/ogmios/releases/tag/v6.14.0.2) and Kupo [v2.11.0.1](https://github.com/IntersectMBO/kupo/releases/tag/v2.11.0.1)) can be used to test for van Rossem compatibility
* It was pointed out that for the time being, forked, van Rossem compatible repos, are going to continue to be considered as viable with IO backed maintenance
* Issue being reported by Indigo labs, [CPU overspend issue on preprod](https://github.com/IntersectMBO/cardano-node/issues/6600), was close with user confirmed they were using an older lucid with hard coded values which is unrelated to the node
* Adoption of Node 11.0.1 and DBSync 13.7.1.0 continues to increasy steadily
* According to [PoolTool](https://pooltool.io/networkhealth), nodes self reporting v11 are at 55% and blocks protocol version 11 in the current epoch is at 76%
* According to [Cexplorer](https://cexplorer.io/hardfork?block=5_days), block production v11 in the last 5 days is at more than 85%
* [Readiness tracker](https://docs.google.com/spreadsheets/d/1ECoYFCtrRtFX3BvqfhaZi6FxlXQMoTGP/edit?gid=960883614#gid=960883614) has been updated:
* Mainnet submission readiness checklist in the summary tab is having its readiness numbers that are based on items considered to be on the critical path
* Exchanges readiness is represented as sum of liquidity stakes from each exchange that is considered ready
* Few light wallets and few tools have become ready
* Dapps continued and focused on adjustments and testing aginst Preview ahead of the PreProd fork where they will continue their testing efforts
* PreProd hard fork initiation governance action was enacted on **10th June**
* Go/No-go Mainnet hard fork initiation governance action submission call date - **15th June**
* Readiness tracker mainnet submission checklist will be adjusted if needed, to be compliant with the hard fork submission policy
* **Guardrails**
* Technical Steering Committee considers no guardrail scripts changes have been made nor there were any constitutional changes in relation to van Rossem hard fork
* Civics Committee reaffirms that they didnt find any issues in the "Consistency with Guardrails" section
* **Governance action metadata**
* Proposed [mainnet hard fork initiation governance action metadata](https://docs.google.com/document/d/1Yfyq9RvsCPblNborLC1wo03-rbU3zF1O1mIddETpSDs/edit?tab=t.0) is 99% the same as the metadata used on Preview+PreProd with updates since PreProd have been
* Citing updated performance report for node 11.0.1 (now available to be linked)
* Citing the related correct protocol parameter change (was different per network)
* Citing monday 15th June (go-no-go) as day when TSC and HFWG have formally recommended submission
* Pending changes
* inclusion of security audit reports for newer ledger rules, plutus implementation
* fix to plutus data structure labelling
* **Security audit(s)**
* Any recent security security audits completed for the code going into this hard fork will be considered for inclusion in the van Rossem hard fork initiation governance action metadata
* In the wake of any critical issue being potentially discovered on PreProd after the hard fork governance action has been submitted on mainnet, Technical Steering Committe will recommend Constitutional Committee to withhold their votes until the issues has been resolved
* Plutus Cost Model parameter update governance action has been submitted on mainnet on 26th of May and its at \~55% approval with the reasonable expectation that it will end up being ratified and subsequently enacted in the next \~3 weeks
* Comms team meetings are happening weekly and async communication continuously. The team that includes representatives from five big Cardano entities, is having a strong grip on a timely, precise, transparent and consistent messaging being made public
* Risk log has been slightly adjusted and some risks had their likelihood reduced
* Ogmios/Kupo maintenance and technical support has been added as a new risk considering the current path forward
* Tech support team is expected to produce draft of the tech support process and resource tracker and to update the hard fork working group on the status of them
* 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)
* [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**
* **Ryan:** Draft and complete hard fork governance action metadata before the go/no-go call on Monday, 15th June
* **Ian/Larisa:** Adjust messaging on Ogmios/Kupo path forward with forked one being considered as the right tool for the time being
* **Leonard:** Check with John L. on the availability of Ogmios/Kupo docker versions
* **Bosko:** Adjust readiness tracker if needed to make sure it correctly reflects hard fork submission policy
* **Bosko:** Update hard fork working group on technical support documents status (process and resources tracker)
---
# 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/11th-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.