> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-technical-steering-committee/tsc-budget-2026-2027/hard-fork-working-group-stipend.md).

# Hard Fork Working Group Stipend

Part of WP2 — Protocol Governance and Evolution in the TSC Support 2026 budget, a Cardano treasury grant administered by Intersect.

### Purpose

The Hard Fork Working Group coordinates ecosystem readiness for Cardano hard forks — making sure node implementations, wallets, tooling, exchanges, SPOs and governance participants are ready before a hard fork is enacted, and that risks and missing dependencies surface early. This programme funds that coordination formally for the 12-month budget period.

### Scope for this period

The focus is the **Protocol versions 12 and 13 (Dijkstra) hard forks**, which bring Linear Leios (CIP-164), nested transactions (CIP-118), Peras (CIP-140), fair min fees (CIP-23), pledge-leverage rewards (CIP-50), Plutus V4 and other ledger changes, and — for the first time — constitutional changes alongside technical ones. See the [Dijkstra upgrade overview](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-overview) for the full list. The working group covers:

* Tracking ecosystem readiness against an agreed readiness framework
* Coordinating dependency and risk tracking across teams, including technical, ecosystem and security concerns
* Outreach to affected groups (SPOs, wallets \[including hardware wallets], exchanges, tooling, DReps, dApps, Intersect members, and the general Cardano community)
* Liaison with the Parameter Committee and Civics Committee on new guardrails and initial parameter settings, and with the constitutional amendment process
* Liaison with Intersect's Security Council on security-related issues
* Post-fork retrospectives
* Coordination with Intersect and developer teams (including node diversity, quality assurance, and performance evaluation)

### Budget and limits

| Item         | Detail                                                         |
| ------------ | -------------------------------------------------------------- |
| Budget       | 144,000 ADA (≈ $36,000 at the proposal's $0.25 reference rate) |
| Seats        | Up to 6 funded experts                                         |
| Compensation | 2,000 ADA per expert per month                                 |
| Settlement   | ADA                                                            |

Compensation is fixed in ADA and does not track the USD price.

### The role

Each funded expert takes responsibility for one or more readiness areas (for example SPOs, wallets, exchanges, tooling, alternative nodes, or governance), keeps its status current, and raises problems early. A short monthly note on what they've done is enough evidence for payment.

### Who can take part

Funded experts are selected against published criteria: relevant hands-on experience; prior hard fork involvement; capacity to commit to regular meetings.

Existing working group members move directly into the funded roles so that Dijkstra preparation is not interrupted; open recruitment fills any remaining seats up to the cap. Seats are non-exclusive: there is no forced rotation, but any vacancy is filled through open recruitment, and members are reconfirmed at the interim review. Anyone can still take part in the working group unfunded.

**Current funded members:** TBD

### Conflict of interest

Funded members disclose relevant affiliations on appointment and refresh the disclosure at the interim review, and recuse themselves where they have a conflict.

### Payment

Paid monthly in ADA against evidence of active participation that month — the monthly note, meeting attendance, and minutes.

### Outputs

* Readiness framework and status tracking for the Dijkstra hard forks
* Meeting minutes, published \[location, cadence]
* Outreach material for affected groups
* A retrospective after each hard fork

### Reporting

* **Interim review:** \[date, \~Month 6]
* **Year-end review:** Month 12 delivery and accountability report

Both are published on this GitBook.

### Contact

Email: <hard-fork@intersectmbo.org>

Program lead: Kevin Hammond (TSC Chair)


---

# 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://committees.docs.intersectmbo.org/intersect-technical-steering-committee/tsc-budget-2026-2027/hard-fork-working-group-stipend.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.
