# Submitting Proposals

## Submitting Proposals in TheStandard Protocol

Submitting proposals is a key way for community members to actively shape the future of TheStandard protocol. Currently, we use Discord as our primary platform for proposal submissions and discussions. Here's a comprehensive guide on how to submit and manage your proposals.

### Current Proposal Submission Process

#### Step 1: Join Our Discord

If you haven't already, [join TheStandard's Discord server](https://discord.gg/thestandard-io-836907456743079956). This is where all initial proposal discussions take place.

#### Step 2: Navigate to the Proposals Channel

Head to our dedicated proposals channel: <https://discord.com/channels/836907456743079956/923347858369949706>

This channel is specifically for proposal submissions and related discussions.

#### Step 3: Draft Your Proposal

Before posting, draft your proposal carefully. A well-structured proposal should include:

* **Title**: A clear, concise title that summarizes your proposal
* **Summary**: A brief overview of what you're proposing
* **Motivation**: Why this proposal is important for TheStandard
* **Specification**: Detailed description of what you're proposing
* **Benefits**: Expected positive outcomes
* **Potential Drawbacks**: Any potential risks or negative consequences
* **Timeline**: Proposed implementation timeline, if applicable

#### Step 4: Post Your Proposal

Share your drafted proposal in the designated Discord channel. This initiates the community discussion phase.

#### Step 5: Engage in Discussion

* Be prepared to answer questions and address concerns from community members
* Be open to feedback and suggestions for improving your proposal
* Actively participate in the discussion to refine and strengthen your proposal

#### Step 6: Refine Your Proposal

Based on community feedback, you may need to revise and refine your proposal. This iterative process helps ensure that the final proposal is robust and well-considered.

#### Step 7: Formal Submission

Once your proposal has been thoroughly discussed and refined, it may be moved to a formal vote on Snapshot. This step typically involves coordination with TheStandard's core team.&#x20;

### Best Practices for Proposal Submission

1. **Research Thoroughly**: Ensure your proposal doesn't duplicate existing features or previously rejected ideas.
2. **Be Clear and Concise**: While details are important, make sure your main points are easy to understand.
3. **Consider All Stakeholders**: Think about how your proposal affects different users of the protocol.
4. **Be Responsive**: Actively engage with comments and questions about your proposal.
5. **Be Patient**: The discussion and refinement process can take time. This thoroughness is crucial for good governance.
6. **Seek Support**: If you're unsure about aspects of your proposal, don't hesitate to ask for help from more experienced community members.

### Future Plans

We're constantly working to improve our governance processes. In the future, we plan to implement a more structured proposal submission system, potentially including:

* A dedicated web portal for proposal submissions
* Standardized proposal templates
* An integrated system for proposal tracking from submission to implementation

Stay tuned for announcements about these improvements!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thestandard.io/tst/governance-and-dao/submitting-proposals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
