> 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-budget-committee/archive/drep-knowledge-journey/stage-1-introduction-to-the-budget-process.md).

# Stage 1: Introduction to the Budget Process

Objective: Understand the purpose and structure of Cardano’s budget process.

## Content:

### Overview of the budget process

&#x20;Importance of budgeting for ecosystem growth

{% embed url="<https://youtu.be/3citdqh6wvI?feature=shared>" %}

### Budget Buckets

{% content-ref url="/pages/h3jMvhl0piqSN3uLnpqc" %}
[Budget Buckets](/intersect-budget-committee/archive/drep-knowledge-journey/stage-1-introduction-to-the-budget-process/budget-buckets.md)
{% endcontent-ref %}

### Quick Summary of the Cardano Budget 2025

<details>

<summary>2025 Budget Overview  </summary>

🔹Estimated budget: 200m - 500m [$ADA](https://x.com/search?q=%24ADA\&src=cashtag_click) &#x20;

🔹Each committee has a dedicated budget, overseen by the Budget Committee for efficient and impactful fund use.

</details>

<details>

<summary>Pre-requisites for a Treasury Withdrawal </summary>

🔹Net Change Limit: A defined cap on the maximum ADA that can be withdrawn within a set period, specified via an info action, e.g., 73 epochs and 350m [$ADA](https://x.com/search?q=%24ADA\&src=cashtag_click)&#x20;

🔹Budget Info Action: A detailed budget breakdown must be approved before any treasury withdrawal can occur.

</details>

<details>

<summary>Leveraging Funds in Voting</summary>

🔹 $ADA from the budget may be used in voting processes. Intersect currently does not recommend voting with the ADA, and will follow DRep recommendations as to when voting would be appropriate with the ADA withdrawn via treasury action.

🔹 Decisions ultimately rest with Intersect members, the DReps, and the Constitutional Committee, keeping power in the hands of the community

</details>

<details>

<summary>Delegation to SPOs</summary>

🔹 Funds received via treasury withdrawal could be delegated to SPOs. A working group will be proposed to determine where (e.g. solo stake pool operators, less than X delegation, more than Y delegation, etc), how long (monthly, quarterly, etc) and how much (5m increments? 10m?)

&#x20;

</details>

<details>

<summary>Active Budget Management</summary>

🔹 Limited to SPO delegations in 2025&#x20;

🔹 Safety and responsible management of funds are top priorities

</details>


---

# 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-budget-committee/archive/drep-knowledge-journey/stage-1-introduction-to-the-budget-process.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.
