> 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/31st-march-2026.md).

# 31st March 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/24th-march-2026#action-items-and-next-steps) - Bosko
2. HFWG meeting time
3. [Haskell node](https://github.com/IntersectMBO/cardano-node/releases) - Jeff and/or Ramsay
4. Plutus cost model - Ryan
5. [Hard Fork Tentative Timeline](https://app.excalidraw.com/l/6GdMPTId7vW/1xnslUPryZP?__r=1773152516515)
6. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724)
7. No X space this week
8. Future hard fork scope (Dijkstra)
   1. Workshop in Porto early June - Amaru team, reach out to Damien (sp0ty) on Discord
9. AOB

#### Key materials

* [Recording](https://drive.google.com/file/d/10hzOJOZjBb47QmExDSKTfu7KS_A1QgXQ/view?usp=drive_link)
* [Chat](https://drive.google.com/file/d/1qg1hiymCYXR4BD8hWN6-_mOdUFJBiyIP/view?usp=drive_link)
* [Transcript](https://docs.google.com/document/d/1sP_gMD_b91IhmRXwlR3DkZNxyfo_SDFh6OiHWRnBapY/edit?usp=drive_link)
  * [Summary and action items](https://docs.google.com/document/d/1sP_gMD_b91IhmRXwlR3DkZNxyfo_SDFh6OiHWRnBapY/edit?tab=t.buy2q156wwi3#heading=h.wrn6h6x4r1lm) (generated by AI from meeting's transcript and chat)
* 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

* **Ramsay / Alexey:** Provide a technical update in Discord regarding the root cause of the v10.7 heap size increase following the performance touchpoint on Thursday.
* **Bosko / Ramsay:** Coordinate with the Release Management team to flip the meeting times starting next week: move the Release Meeting to 2:00 UTC and the Hard Fork Working Group to 3:00 UTC to ensure the HFWG has the freshest data.
* **Ryan Williams:** Update the Excalidraw Timeline to include the v11.0 promotion milestone and clear labeling for exchange integration windows.
* **Bosko:** Formally publish the van Rossem Risk Register for community visibility and assign owners to each risk by the next meeting.
* **Ryan Williams:** Present the iterated "Technical Change Short-listing" process at next week's meeting, incorporating feedback from the recent Builderfest.


---

# 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/31st-march-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.