> 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/3rd-march-2026.md).

# 3rd March 2026

#### Agenda

1. [Action items from the last call](https://cardanoupgrades.docs.intersectmbo.org/proposed-intra-era-scope/hard-fork-working-group-meeting-minutes/24th-february-2026#action-items-and-next-steps) - Bosko
2. [van Rossem upgrade readiness page updates](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/van-rossem-upgrade-readiness) - Bosko
3. SanchoNet update - Ryan Williams
   1. 10.6.2
4. [Haskell node](https://github.com/IntersectMBO/cardano-node/releases) - Jeff/Ramsay
   1. 10.7.0
   2. Payload of Features in the hard fork build
5. Weekly X spaces - Inside the van Rossem Upgrade: Weekly Community Q\&A
   1. [Luma calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif)
   2. [This weeks X space](https://x.com/i/spaces/1dKrPErbgbOJX?s=20)
6. Future hard fork scope collecting - On-chain surveys and polls - Ryan Wiley
7. AOB

#### Key materials

* [Recording](https://drive.google.com/file/d/1oZWcH9VG295cjtvdVXoKheTmaQKAhm0M/view?usp=sharing)
* [Chat](https://drive.google.com/file/d/1IHDX8fvq1jUNTi_C6nEcQCKXTu_hDPw-/view?usp=sharing)
* [Transcript](https://docs.google.com/document/d/10GGoO-gM0CUkon-4qpYNAwQUxJeYEIlV0tx3VA3HPDE/edit?tab=t.0#heading=h.131j0mny10u1)
  * [Summary and action items](https://docs.google.com/document/d/10GGoO-gM0CUkon-4qpYNAwQUxJeYEIlV0tx3VA3HPDE/edit?tab=t.m37rmktgfzyu#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/1dKrPErbgbOJX?s=20)
* [Tentative timeline](https://app.excalidraw.com/s/6GdMPTId7vW/1xnslUPryZP)

#### Action items and next steps

1. **Ramsay Taylor / Alexey Kuleshevich:** Provide a definitive status update on the Node v10.7 release candidate in the Discord channel following today's Release Management meeting.
2. **Ryan Williams:** Share examples of the new Plutus built-ins in this week's upgrade bulletin once the Sanchonet cost model is enacted and verified.
3. **Ryan (Cerkoryn):** Finalize the Label 17 CIP and shared validation library to ensure consistent JSON metadata across community tooling.
4. **Kevin Hammond / Ryan Williams:** Review the Dijkstra feature list and define a process for selecting which items are "voted on" using the new polling tool.
5. **Bosko Majdanac:** Ensure the Weekly Community Q\&A (X Space) is promoted across social channels to facilitate direct ecosystem feedback.
6. **Kevin Hammond:** Present the Dijkstra short-listing PoC to the Technical Steering Committee (TSC) tomorrow for further organizational alignment.
7. **Ken-Erik Ølmheim:** Provide the biographical/background materials for Max van Rossem to be included in the formal hard fork rationale/metadata.


---

# 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/3rd-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.