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

# 7th April 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes/31st-march-2026#action-items-and-next-steps) - Bosko
2. [Haskell node](https://github.com/IntersectMBO/cardano-node/releases) - Jeff and/or Ramsay
3. [Hard Fork Tentative Timeline](https://app.excalidraw.com/l/6GdMPTId7vW/1xnslUPryZP?__r=1773152516515)
4. [Risk log](https://docs.google.com/spreadsheets/d/1DSAiayrPOhhzSKKKljbd2WxHQPFmzKsvoyyA-BJUDg8/edit?gid=1105903724#gid=1105903724)
5. No X space this week
6. Discord channel
   1. Making it open for read to anybody
7. Future hard fork scope (Dijkstra)
   1. Reminder - Workshop in Porto early June - Amaru team, reach out to Damien (sp0ty) on Discord
   2. [Shortlisting Technical Changes as presented by Ryan Williams at Buidler Fest in Argentina](https://docs.google.com/presentation/d/1ZkHPXWxuwDLyz-zTSEP_64izf09Gl6X9TryVHSk3KEs/edit?slide=id.p1#slide=id.p1)
8. AOB

#### Key materials

* [Recording](https://drive.google.com/file/d/1SKGovtH9xWgZcFQv1qm18aZihS4mr7F2/view?usp=drive_link)
* [Chat](https://drive.google.com/file/d/17idSzeSUcmWon4FsLmrtU7F29HSN_wIg/view?usp=drive_link)
* [Transcript](https://docs.google.com/document/d/1ylTFhFUo_34w8CBELYUzdDIiKlAtwDn9-3L79qPu1Mk/edit?usp=drive_link)
  * [Summary and action items](https://docs.google.com/document/d/1ylTFhFUo_34w8CBELYUzdDIiKlAtwDn9-3L79qPu1Mk/edit?tab=t.q6auokpwmhjp) (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

* Alexey Kuleshevich / Performance Team: Conduct integration benchmarks for the potential Ledger memory fix. If successful, prepare the v10.7.1 backport immediately to avoid delaying the v11.0 hard fork node.
* Bosko: Refine the X Space / Community Engagement strategy to target specific stakeholder groups (e.g., a session specifically for SPOs or DApp/DEX developers) to increase participation.
* Bosko: Finalize the background list of all ecosystem stakeholders and contact points to ensure targeted communications for the v11.0 upgrade.
* Bosko: Finalize the open Discord HF channel permissions to allow public "read-only" access for non-Intersect members by next week.
* Ryan Williams: Share the Builderfest recording on technical short-listing once available to incorporate broader community feedback into the Dijkstra scoping process.


---

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