> For the complete documentation index, see [llms.txt](https://wiki.shellprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.shellprotocol.io/shell-dao/governance-process/governance-stages.md).

# Governance Stages

## Stage 1: Request for Comment (RFC)

In the initial stage, the author posts an RFC to the Shell governance forum on Commonwealth. Anyone may author and post an RFC. To create an RFC, navigate to the Proposals Category on Commonwealth and create a new topic.

* Forum post title must follow the format: "RFC: \[Category]/\[Your Proposal Title]"
* The text of the post must follow the format in [Proposal Template](/shell-dao/governance-process.md#proposal-template).
* Have an idea for an RFC? Before making a formal post, consider first sharing your thoughts, concerns, or goals on the forum to get early feedback or co-authors. You may then link to this discussion when you post the RFC.

Forum moderators will check that RFCs follow the correct format. If there are any issues, the author will be notified and invited to repost the RFC properly.

## Stage 2: Discussion <a href="#step-1-write-request-for-comment-rfc" id="step-1-write-request-for-comment-rfc"></a>

During this stage, the community can provide feedback and help author(s) modify or revise the proposal. It is recommended to allow **at least one week** for open discussion. Complicated or controversial proposals may benefit from a longer discussion period.

* Authors are expected to be active participants in the forum discussion.
* As the author, you are the champion of this proposal! It's up to you to promote the RFC, get feedback and inspire voters.
* Consider using supplemental discussion platforms, such as Discord or Twitter spaces.
* Reach out to veSHELL delegates for their support.
* Be open to making changes to your proposal as needed.

## Stage 3: Snapshot Vote <a href="#step-1-write-request-for-comment-rfc" id="step-1-write-request-for-comment-rfc"></a>

Once the author(s) consider the proposal finalized, it's time to move to a vote.

The Snapshot process begins when an address with at least 2000 veSHELL (individually or by delegation) posts a Proposal that meets all of the required specifications.

A valid Snapshot vote must adhere to the following.

* The proposal must provide a link to the forum post of the respective RFC.
* The order of vote options must be as follows. (The order is important to reduce noise resulting from users who always just click the first option.)
  1. ABSTAIN
  2. NO
  3. YES
* The vote must run for **10 days**.
* The vote must have a quorum of **10% of the total supply** of veSHELL, as measured at the block it was proposed.
* If the proposal receives **more “YES” votes than "NO" votes**, it will be considered “Passed”.
* If applicable, the linked payload must match the specification.

One veSHELL token = one vote.

If a vote fails, it will not be executed. You may post it again to Snapshot for a re-vote, but you are encouraged to wait at least **one month** before doing so, unless other circumstances have meaningfully changed. This is to reduce spam and be considerate of the time and energy required for proper governance.

{% hint style="info" %}
A Snapshot vote that fails to meet all of the above requirements will not be valid, even if it wins a majority of the votes.

If you're unsure, don't be shy! Ask for help.
{% endhint %}

## Stage 4: Results and Execution <a href="#step-1-write-request-for-comment-rfc" id="step-1-write-request-for-comment-rfc"></a>

If a vote requiring on-chain activity passes, the [DAO Multisig](/shell-dao/dao-multisig.md) must then execute the vote as soon as possible, at maximum within **one week**. Upon transaction execution, community moderators are expected to post a comment on the forum thread with a link to the transaction.

In case of a delay, multisig signers must post regular updates to the Forum on the Proposal's thread providing an explanation and relevant details.

Keep in mind the DAO's on-chain capabilities are limited. All other votes will be executed off-chain following the steps described in the proposal.


---

# 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 dynamically by asking a question.

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

```
GET https://wiki.shellprotocol.io/shell-dao/governance-process/governance-stages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.