> 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/technical-expert-event-attendance.md).

# Technical Expert Event Attendance

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

### Purpose

This program pays for technical experts to represent Cardano at major events, where they explain Cardano's technology — Leios, Peras, the Dijkstra upgrade, governance and more — to the wider community and to DReps. The aim is clear, informed technical communication, not general attendance.

### Budget and limits

| Item       | Detail                                     |
| ---------- | ------------------------------------------ |
| Budget     | $24,000 for the year                       |
| Experts    | Around 12 trips (≈ $2,000 each on average) |
| Covers     | Economy flights and accommodation          |
| Settlement | USD, reimbursed against receipts           |

### Which events

We keep a short list of qualifying events, reviewed every quarter. It is not limited to the events named in the original budget proposal.

**Current shortlist:** RareEvo, Cardano Africa Tech Summit, European Blockchain Convention, CV Summit Zurich, Node Diversity Workshops

You can also propose an event that isn't on the list, if it fits the purpose above.

### Who can apply

Technical experts who can represent Cardano's technology credibly. Priority goes to people with a **confirmed speaking or panel role**. For a Cardano presence at an externally run event, confirm your slot with the organizer before applying.

### How to apply

Apply as early as you can — flights and hotels get more expensive closer to the event. Tell us:

* Your name and the event
* Your role there (speaking, panel, or attending)
* Estimated flight and accommodation cost
* How your attendance helps explain Cardano's technology to the community

Apply via: [TSC Events/Travel Request](https://forms.clickup.com/9015279944/f/8cnmga8-54195/F567LG5DR0SK8AKOLJ)

### How decisions are made

The WP1 lead approves applications against the remaining budget, prioritizing confirmed speaking roles. Applicants disclose any relevant affiliations; anyone with a conflict does not take part in the decision.

### After the event

* Costs are reimbursed against receipts
* A short note on what you presented and what came out of it, within \[two weeks] of the event
* The list of funded attendees is published

### 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/technical-expert-event-attendance.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.
