> 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/parameter-committee-stipend.md).

# Parameter Committee Stipend

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

### Purpose

The Parameter Committee gives independent technical advice on Cardano's protocol parameters: proposed parameter changes, the guardrails that bound them, and the initial settings for new parameters introduced at hard forks. Its recommendations inform DReps, SPOs and the Constitutional Committee before they vote. This programme funds committee members' time, and commissions independent benchmarking studies to give the committee evidence that does not depend on any one node implementation.

### Scope for this period

* Reviewing proposed parameter changes and publishing recommendations, including changes to Plutus execution limits, and stake pool settings as applicable
* Guardrails and initial settings for the new Dijkstra parameters (around 100 for Leios and 50 for Peras)
* Cost model settings for Plutus v4
* Up to four independent benchmarking studies on questions where the committee needs evidence, e.g. Leios throughput limits, fee and reference-script pricing, block and transaction size limits

### Budget and limits

| Item                 | Detail                                                         |
| -------------------- | -------------------------------------------------------------- |
| Committee engagement | 144,000 ADA (≈ $36,000 at the proposal's $0.25 reference rate) |
| Seats                | Up to 12 funded experts                                        |
| Compensation         | 1,000 ADA per expert per month                                 |
| Benchmarking studies | 160,000 ADA (≈ $40,000), up to 4 studies at 40,000 ADA each    |
| Settlement           | ADA                                                            |

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

### The role

Funded members attend committee meetings, review the parameter proposals and guardrails as necessary, and contribute to its published recommendations. A short monthly note on what they've done is enough evidence for payment.

### Who can take part

Members are selected against published criteria: relevant expertise in protocol parameters, network performance, economics or ledger design, and capacity to commit to regular meetings. **Independence from node vendors is a published, checked criterion**, because the committee's advice and the benchmarking studies must not depend on any one implementation.

Existing committee members move directly into the funded roles; 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.

**Current funded members:** TBD

### Benchmarking studies

Studies are separate, deliverable-based engagements, not part of the monthly stipend.

* **Scoping:** the committee agrees a study plan; each study gets a short statement of work (question, method, deadline, acceptance criteria, cap).
* **Selection:** open call \[link to RFP], with conflict-of-interest disclosure from bidders. Node vendors are not eligible to run studies.
* **Payment:** on delivery and acceptance against the criteria.
* **Publication:** results published in full, with the committee's recommendation.

### Conflict of interest

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

### Outputs

* Recommendations on parameter changes and guardrails, published \[location, cadence]
* Meeting minutes
* Benchmarking study reports

### Reporting

* **Interim review:** end of February 2027 (Week 26)
* **Year-end review:** end of August 2027

Both are published on this GitBook.

### Contact

\[Parameter Committee contact]

Program lead: Alexander Moser


---

# 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/parameter-committee-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.
