> ## Documentation Index
> Fetch the complete documentation index at: https://ducs.surchi.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# SURCHI DAO Voting: Cast Your Vote on Protocol Proposals

> Step-by-step guide to participating in SURCHI governance — staking your tokens, reviewing proposals, casting votes, and tracking outcomes.

Governance is not a spectator sport at SURCHI. Every token holder has a voice, and the decisions made through governance directly shape the protocol's direction, economics, and security posture. This guide walks you through everything you need to participate — from staking your tokens for the first time to casting votes and understanding how outcomes are determined.

## Voting Mechanics

SURCHI governance uses a token-weighted, on-chain voting system. Understanding the mechanics ensures your participation counts when it matters most.

| Parameter               | Value                                                     |
| ----------------------- | --------------------------------------------------------- |
| **Voting Power Source** | Staked SURCHI at proposal snapshot block                  |
| **Voting Period**       | 7 days per standard proposal                              |
| **Quorum Requirement**  | Minimum percentage of circulating supply must participate |
| **Standard Majority**   | >50% of votes cast                                        |
| **Supermajority**       | >67% of votes cast (for core protocol changes)            |
| **Snapshot Timing**     | Voting power locked at the block when proposal is created |

<Warning>
  Tokens staked **after** a proposal's snapshot block do not count toward that proposal. Stake early and keep your tokens staked to maintain consistent voting power across all active proposals.
</Warning>

## How to Vote

<Steps>
  <Step title="Stake SURCHI to Earn Voting Power">
    Navigate to the SURCHI staking platform and stake your SURCHI tokens. Staking both earns protocol revenue and grants governance voting power. Your voting weight equals your staked balance at the time a proposal's snapshot is taken.
  </Step>

  <Step title="Navigate to the Governance Forum">
    Visit the [SURCHI Governance Forum](https://surchi.io/governance) to browse active and upcoming proposals. Each proposal includes a title, summary, full specification, and the community discussion thread. Read everything before voting.
  </Step>

  <Step title="Review Proposal Details">
    For each proposal you intend to vote on, carefully review:

    * The **Problem Statement** — what issue the proposal addresses
    * **Proposed Change** — exactly what will happen if the proposal passes
    * **Technical Specification** — on-chain parameters or contract changes involved
    * **Risk Assessment** — potential downsides or failure modes
    * **Community Discussion** — arguments from both supporters and critics
  </Step>

  <Step title="Connect Your Wallet on the Governance Portal">
    Go to the governance voting portal at [surchi.io/governance](https://surchi.io/governance) and connect the wallet that holds your staked SURCHI. Ensure you're on the official URL — bookmark it to avoid phishing.
  </Step>

  <Step title="Cast Your Vote">
    Select the active proposal and choose your position:

    * **For** — you support the proposal as written
    * **Against** — you oppose the proposal
    * **Abstain** — you acknowledge the proposal but decline to vote directionally (counts toward quorum)

    Confirm the transaction in your wallet. Your vote is recorded on-chain and cannot be changed once confirmed.
  </Step>

  <Step title="Monitor the Voting Period and Outcome">
    Track the vote's progress in real time on the governance portal. Once the voting period closes, the result is automatically tallied. If quorum is met and the threshold is reached, the proposal moves to execution. If not, it fails and can be resubmitted with modifications.
  </Step>
</Steps>

## Proposal Types

Different proposal types carry different timelines and approval thresholds, proportional to the significance of the change being made.

| Proposal Type             | Voting Period | Threshold              | Examples                                                                 |
| ------------------------- | ------------- | ---------------------- | ------------------------------------------------------------------------ |
| **Standard Proposals**    | 7 days        | Simple majority (>50%) | Fee adjustments, grant allocations, UI parameters, partnership approvals |
| **Core Protocol Changes** | 14 days       | Supermajority (>67%)   | AI model upgrades, smart contract changes, Sentinel architecture changes |
| **Emergency Actions**     | 24 hours      | Supermajority (>67%)   | Protocol pause, emergency parameter changes, incident response           |

Emergency actions are reserved for genuine time-sensitive situations. Abuse of the emergency track is itself a governance violation.

## Creating a Proposal

Any SURCHI token holder who meets the minimum proposal threshold can submit a formal on-chain governance proposal.

**Requirements to submit a proposal:**

* Hold and have staked the minimum required SURCHI (threshold published in governance forum)
* A written proposal draft that follows the standard proposal template
* Prior community discussion (strongly recommended — see tip below)

**Steps to submit:**

1. Draft your proposal using the official template in the Governance Forum
2. Post it in the **Pre-Proposal Discussion** section and gather community feedback
3. Revise based on discussion — address major objections before going on-chain
4. Submit the formal on-chain proposal through the governance portal
5. Share the on-chain proposal link back to the forum thread so voters can find the discussion

Proposals that skip community discussion and go straight on-chain are less likely to reach quorum and more likely to be voted down, even if the underlying idea is sound.

<Tip>
  Discuss your proposal in the community forum before submitting on-chain. Proposals with strong community alignment pass more consistently. A proposal that fails on-chain cannot be resubmitted unchanged — you'll need to meaningfully revise it first.
</Tip>
