> 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/commissioned-technical-reports.md).

# Commissioned Technical Reports

Part of WP1 — Community-Facing Technical Coordination in the TSC Support 2026 budget, a Cardano treasury grant administered by Intersect.

### Purpose

The Technical Steering Committee (TSC) commissions independent technical reports on questions that matter to Cardano's future, written so that DReps and the wider community — not just engineers — can understand the issues before they vote or decide.

### Budget and limits

| Item       | Detail                               |
| ---------- | ------------------------------------ |
| Budget     | $40,000 for the year                 |
| Reports    | Up to 4, at up to $10,000 each       |
| Settlement | USD, paid on delivery and acceptance |

### This year's topics

| Report                           | Status                          |
| -------------------------------- | ------------------------------- |
| Post-Quantum Cryptography        | Pending RFP                     |
| Alternative node implementations | Pending RFP                     |
| Security readiness               | Pending RFP                     |
| Fourth report                    | Open — chosen later in the year |

### How it works

* **Topics** are chosen by the WP1 lead, roughly one a quarter, based on what's live in governance and community discussion.
* **Authors** are independent experts, chosen through an open call or direct invitation, and must disclose any conflict of interest.
* **Payment** is made on delivery and acceptance against the report's scope.
* **Publication:** every report is reviewed by the WP1 lead and published here in full, crediting the author and reviewer, ahead of any governance vote it is meant to inform.

### Agreed Topics&#x20;

* (1) Post-Quantum Cryptography&#x20;
* (2) Impact of Node Implementations
* (3) Security Readiness

\*sourced from Committee [Meeting Minutes Septemeber 30, 2026](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/meeting-minutes/2026-tsc-meeting-minutes/meeting-minutes-september-30-2026.md)

### Published reports

Coming Soon..&#x20;

### Reporting

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

Both are published on this GitBook.

### Contact

Program lead: Christian Taylor


---

# 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/commissioned-technical-reports.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.
