> For the complete documentation index, see [llms.txt](https://docs.hydra-voting.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hydra-voting.intersectmbo.org/budget-process/budget-process-faqs.md).

# Budget Process FAQs

Frequently asked questions about 2026 Budget Process facilitated by Intersect

## Submitting a Proposal

<details>

<summary>Why do I need to donate 1,000 ADA?</summary>

The 1,000 ada donation is a non-refundable payment to the Cardano Treasury (not to Intersect) required to enter the process. It must be paid from the same wallet used to submit your proposal, so reviewers can verify identity and wallet ownership. One donation per proposal, multiple submissions require separate donations.

The requirement originated from DReps, not Intersect, and has strong support from both DReps and vendors. The 1,000 ada figure balances discouraging low-effort submissions without being prohibitive. This requirement only applies to this process - direct on-chain submissions don't require it.

**Making the donation does not guarantee** proposal approval, on-chain execution, funding, or that Intersect will act as Administrator.

</details>

<details>

<summary>Do I need to donate again if I update my proposal?</summary>

No.\
The donation is required **once per proposal**, not per update.

</details>

<details>

<summary>Can I save my proposal and come back later?</summary>

Yes.\
You can save your proposal as a **draft** and return to it later.

</details>

<details>

<summary>What happens after I submit my proposal?</summary>

* Your proposal becomes **Live**
* Feedback and comments begin
* You can update and re-submit your proposal

</details>

## Updating a Proposal

<details>

<summary>Can I edit my proposal after submitting it?</summary>

Yes — during the **feedback phase**, before Hydra voting starts.

</details>

<details>

<summary>Why can’t I save changes when editing?</summary>

For Live proposals:

* There is **no Save option**
* Changes are applied only after clicking **Re-Submit Proposal**

👉 Leaving the page without re-submitting will discard changes

</details>

<details>

<summary>What is a “new version” of a proposal?</summary>

Each re-submission creates a **new version**:

* Previous versions remain visible
* Changes can be tracked

</details>

<details>

<summary>Do I need to confirm legal declarations again when updating?</summary>

Yes.\
Legal declarations must be confirmed **on every submission and re-submission**

</details>

## Comments

<details>

<summary>Who can comment on proposals?</summary>

* DReps
* Community members with a connected wallet

</details>

<details>

<summary>Can I edit my comment?</summary>

Yes — within **15 minutes** of posting.\
After that, comments cannot be edited.

</details>

<details>

<summary>Are comments public?</summary>

Yes.\
All comments are visible to everyone.

</details>

## Hydra Voting

<details>

<summary>When does Hydra voting start?</summary>

Hydra voting begins after the **feedback and iteration phase is complete**.

</details>

<details>

<summary>Can I update my proposal during Hydra voting?</summary>

No.\
Once Hydra voting starts:

* Proposals are **locked**
* No further edits are allowed

</details>

<details>

<summary>Who can vote?</summary>

DReps participate in Hydra voting using their connected wallet.

</details>

<details>

<summary>What happens after Hydra voting?</summary>

Proposals that receive sufficient support:

* Move forward to **on-chain treasury withdrawal**
* May be funded if approved on-chain

</details>

## Other

<details>

<summary>Can I submit multiple proposals?</summary>

Yes.\
Each proposal requires a **separate 1,000 ADA donation**.

</details>

<details>

<summary>Can I withdraw my proposal?</summary>

*(Include only if available to non-admin users)*

Yes, proposers can withdraw their proposal.\
This action cannot be undone.

</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://docs.hydra-voting.intersectmbo.org/budget-process/budget-process-faqs.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.