> 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/28th-april-2026.md).

# 28th April 2026

#### Agenda

1. Expectations alignment - Bosko
2. Meeting cadence - Bosko
3. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/21st-april-2026#action-items-and-next-steps) - Bosko
4. [Haskell node](https://github.com/IntersectMBO/cardano-node/releases) - Sam/Ramsay/Jeff
5. [Van Rossem Upgrade Update](https://docs.google.com/presentation/d/1pEFh_GC3Nx2nTVPXj9bke9R7C9Bkr8Hk/edit?slide=id.p1\&pli=1#slide=id.p1) - Bosko, all
   1. Readiness tracker
6. [Hard Fork Detailed Timeline](https://app.excalidraw.com/l/6GdMPTId7vW/1xnslUPryZP?__r=1773152516515)
7. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724)
8. Plutus Cost Model
9. AOB

#### Key materials

* [Summary and action items](https://docs.google.com/document/d/1FZ0_6yvOzonlcWU2546G4OIT1pFvUUgDR1Mpi4cQbDA/edit?tab=t.k4fxadxr45wu)
* 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)
  * [This weeks X space](https://x.com/i/spaces/1RKjpzdjXMeJw?s=20)
* [Tentative timeline](https://app.excalidraw.com/s/6GdMPTId7vW/1xnslUPryZP)

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

* **Samuel Leathers / IO Team:** Tag and release DB-Sync 13.7.0.4 (expected today/tomorrow) and prepare to promote Node v11.0 to Mainnet-ready status next week.
* **Bosko Majdanac:** Draft a formal Communications Plan by next meeting to address the rollout of protocol parameters and stakeholder engagement.
* **Bosko Majdanac / Leonard Hegarty / Samuel Leathers:** Schedule a "Show and Tell" technical session (via Google Meet/Discord) to demonstrate to DApp developers how to properly upgrade smart contracts for the new cost models.
* **Bosko Majdanac:** Update the Master Timeline with explicit epoch boundaries to reflect the May 28th submission target and June enactment.
* **Leonard Hegarty:** Continue outreach to DApp developers (specifically those using Aiken) to ensure they are testing against the v10.7.1/v11.0 builds.
* **Terence McCutcheon:** Circulate the finalized instructions and link for the publicly accessible Discord channel.
* **Bosko Majdanac:** Prepare the Readiness Tracker in a centralized Sheets file to granularly track the "percentage of completion" for each ecosystem tool and library.
* **Kevin Hammond / Ryan Williams:** Finalize metadata to ensure the Committee Minimum Size reduction is chained correctly to the Plutus parameter update on Mainnet.


---

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