> 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-proposal-submission/how-to-submit-proposal.md).
# 🗳️How to Submit Proposal
This guide walks you through the full process of creating and submitting a proposal in the Intersect Budget Platform.
{% hint style="info" %}
## Recommendation
The Budget form requires many details, it's recomended to **draft your proposal first on a document**.
You can find [here](https://budgetcommittee.docs.intersectmbo.org/cardano-budget-process/budget-proposal-submission-template-download) a downloadable template
{% endhint %}
{% stepper %}
{% step %}
### Step 1: Connect your wallet
1. Click **Connect Wallet** in the top right corner
2. Select your preferred option:
* Connect Wallet (CIP-95 compatible wallet)
* CardanoSigner
* DRep Key / Stake Key
3. Select your wallet (e.g. Eternl)
4. Sign it with your stake key/DRep key
Once connected, your wallet will be linked to your session.
{% hint style="warning" %}
The **same wallet MUST be used for proposal submission and treasury donation, in order to verify it**
{% endhint %}
{% endstep %}
{% step %}
### Step 2: Go to Proposals
1. Click **View Proposals** in the top navigation
2. You will land on the proposals page
From here you can:
* View existing proposals
* Create a new proposal
* Access your drafts
{% endstep %}
{% step %}
### Step 3: Start a new proposal
1. Click **+ Create New Proposal**
You will enter the proposal submission flow.
{% endstep %}
{% step %}
### Step 4: Review important requirements
Before continuing, you will see an **IMPORTANT notice**.
To proceed:
* You must complete a **1,000 ADA non-refundable treasury donation**
* The donation must be made from the **same wallet** you are connected with
* A separate donation is required for each proposal
Confirm by checking the acknowledgment box, then click **Continue**
{% hint style="danger" icon="circle-exclamation" %}
### Treasury Donation
* A **1,000 ADA donation is required per proposal**
* Submission does **not guarantee funding**
* The same wallet must be used throughout the process
* Legal declarations must be confirmed on every submission or edit
***
For details on how to submit your treasury donation refer to [this guide](/budget-process/budget-proposal-submission/how-to-donate-to-the-cardano-treasury-1-000-ada.md)
{% endhint %}
{% endstep %}
{% step %}
### Step 5: Complete your proposal
You will complete the proposal form, organized into the following sections:
#### 1. Proposal Overview
Basic information about your proposal (title, summary)
#### 2. Alignment to Strategy Framework
How your proposal aligns with Cardano’s strategic priorities
{% embed url="" %}
#### 3. Proposer
Information about the submitting individual or entity
#### 4. Proposal Details
Detailed description of the work and expected outcomes
#### 5. Budget Administration
Administrative setup, including delivery and oversight
#### 6. Budget Summary
Total budget and breakdown
#### 7. Other Supporting Info
Optional links or additional materials
#### 8. Treasury Donation Verification
* Provide the **transaction hash** for your 1,000 ADA donation
* Confirm the required checkbox
{% hint style="danger" icon="circle-exclamation" %}
### Treasury Donation
* A **1,000 ADA donation is required per proposal**
* Submission does **not guarantee funding**
* The same wallet must be used throughout the process
* Legal declarations must be confirmed on every submission or edit
***
For details on how to submit your treasury donation refer to [this guide](/budget-process/budget-proposal-submission/how-to-donate-to-the-cardano-treasury-1-000-ada.md)
{% endhint %}
#### 9. Legal Declarations
You must:
* Provide submitter details (name, email, role)
* Confirm all required declarations
{% hint style="info" %}
These declarations must be confirmed **every time you submit or re-submit a proposal**
{% endhint %}
{% endstep %}
{% step %}
### Step 6: Save and manage your draft
While working on your proposal:
* Click **Save** to store progress
* Click **Save & Exit** to leave and return later
* Access drafts via **My Dashboard → My Proposals / Drafts**
{% hint style="info" %}
The form is also **auto-saved every 2 minutes**
{% endhint %}
{% endstep %}
{% step %}
### Step 7: Preview your proposal
Before submitting:
* Click **Preview Proposal**
This allows you to review how your proposal will appear to others.
{% endstep %}
{% step %}
### Step 8: Submit your proposal
When ready:
1. Click **Submit Proposal**
2. Ensure:
* Donation hash is provided
* Legal declarations are confirmed
Once submitted:
* Your proposal becomes visible on the platform
* It enters the **feedback and iteration phase**
{% endstep %}
{% endstepper %}
***
## What happens next
### After submission
* DReps and the community can comment on your proposal
* You can update your proposal based on feedback
* Each update creates a **new version with tracked changes**
{% hint style="info" %}
You can continue refining your proposal until finalization
{% endhint %}
### Before Hydra voting
#### Before voting begins
* Ensure your proposal reflects the latest updates
* Address feedback where relevant
{% hint style="info" %}
## Once Hydra voting starts
* Your proposal will be **locked**
* No further edits can be made
{% endhint %}
---
# 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-proposal-submission/how-to-submit-proposal.md?ask=&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.
