> 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/16th-december-2025.md).

# 16th December 2025

#### Agenda

1. [Proposed intra-era scope](https://intersectmbo.org/news/proposed-intra-era-hard-fork-to-protocol-version-11) and community feedback
2. Ratify proposed naming of the intra-era hard fork
3. [Readiness list](/van-rossem-upgrade/van-rossem-upgrade-readiness.md) and [Submission criteria](/general/hardfork-initation-submission-policy.md)
   1. [Draft: Update policy to include alternative node implementations and Midnight](https://github.com/IntersectMBO/hf-wg-documentation/pull/33)
4. Timings on testnet forks
5. Timing of Plutus cost model update after hard fork, considering other parameter changes around similar times
6. [Requests for next session agenda and the date of the next meeting](https://cardanoupgrades.docs.intersectmbo.org/proposed-intra-era-scope/hard-fork-working-group-meeting-minutes/13th-january-2026)
7. Dijkstra Era scope collecting

#### Key materials

* [Recording](https://drive.google.com/file/d/1w1hDgIU8W2CJWq4_-m-N20dOIuVC8Jdu/view)
* [Chat](https://drive.google.com/file/d/13bWId1x5RIxWBvG7UHIMEG3xjBUn79_c/view)
* [Transcript](https://docs.google.com/document/d/1TpZCzN6dtF1cxYowuAH_bL0IZQdBQZZT-85VJLHPFRA/edit?usp=sharing)
  * [Summary and action items](https://docs.google.com/document/d/1TpZCzN6dtF1cxYowuAH_bL0IZQdBQZZT-85VJLHPFRA/edit?tab=t.7mxvlgq2ht69#heading=h.1s5150v1ynw3) (generated by AI from meeting's transcript and chat)

#### Action items and next steps

1. **Hard Fork Policy Update**: Ryan Williams' Pull Request to update the Hard Fork Initiation Submission Policy will be reviewed.
2. **Hard Fork Naming**: Voted proposal to name intra-era hard fork “van Rossem” (named after respected community member Max van Rossem who sadly passed away) will be forwarded to the Technical Steering Committee (TSC) for review and ratification.
3. **Stakeholder Communication**: Kevin Hammond to begin contacting relevant groups (e.g., exchanges, tooling) to make them aware of the pending hard fork and to encourage review of the submission policy and readiness list.
4. **Release Candidate & Testnet**: Jessica Gilbert to post an update on the release candidate and testnet planning in the hard fork working group channel following the release meeting.
5. **Plutus Parameters**: The Plutus team is required to present a cost model parameter proposal, with confirmed benchmarking results, to the Parameter Committee meeting scheduled for January 15, 2026.
6. **Dijkstra Scope Collection**: Ryan Williams is happy to create a 'wish list' repository or HackMD document to start collecting requests and suggested scope for the Dijkstra Era hard fork.
7. **Next Meeting**: The next Hard Fork Working Group meeting is scheduled for January 13, 2026.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cardanoupgrades.docs.intersectmbo.org/general/hard-fork-working-group-meeting-minutes/16th-december-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.