Proposal Process

All governance decisions in GNDX Protocol follow a three-stage process. Each stage serves a distinct purpose and cannot be bypassed (with one limited exception for the Gaming Council on routine index maintenance).

Stage Overview

Stage 1: Temperature Check      Stage 2: Governance Vote      Stage 3: Execution
─────────────────────────────   ──────────────────────────    ──────────────────────
Platform: Snapshot              Platform: Snapshot            Contract: Timelock.sol
Duration: 5 days                Duration: 7 days              Delay: 48h or 7 days
Binding: No                     Binding: Yes (if quorum met)  Permissionless execute
Threshold: >60% approval        Threshold: 66% supermajority  Parameter bounds checked

Stage 1 — Temperature Check

Purpose: Gauge community interest before investing effort in a full on-chain proposal.

• Platform: Snapshot (off-chain, signature-based, zero gas cost)
• Who can post: any address holding ≥ 1,000 veGAME
• Duration: 5 days
• Passes if: >60% approval
• If fails: cannot resubmit for 30 days

This stage filters obvious non-starters before they consume the community's governance attention and the author's gas.

Stage 2 — Governance Vote

Purpose: The binding decision. If this passes quorum and supermajority, the action will execute.

• Platform: Snapshot (off-chain)
• Duration: 7 days
• Quorum: 5% of total circulating veGAME must participate
• Passes if: 66% supermajority of votes cast (FOR + AGAINST) — not 66% of total supply
• Requires precise specification: exact function call, contract address, calldata, expected outcome
• If quorum not reached: fails, can resubmit after 14 days

Supermajority Calculation

66% is calculated as: forVotes × 10,000 / (forVotes + againstVotes) ≥ 6,600

Abstain votes do not count toward quorum or the supermajority threshold.

Stage 3 — Timelock Execution

Purpose: Give the community time to observe the pending action and exit if they disagree before it executes.

After Stage 2 passes:

1. The proposal author submits the exact calldata to Governor.sol
2. The Governor schedules the action in Timelock.sol
3. Standard actions: 48-hour delay
4. High-stakes actions: 7-day delay (see below)
5. After the delay: anyone can call execute() to finalize the action
6. The Governor checks parameter bounds before executing — out-of-bounds execution will revert

High-Stakes Actions (7-Day Timelock)

The following require a 7-day timelock (vs. 48 hours for standard proposals):

• Any treasury allocation > $200K
• Any smart contract upgrade
• Adding new deployment chains
• Removing more than 3 tokens in a single proposal
• Changing tier allocation percentages

Gaming Council Bypass

Gaming Council members (COUNCIL_ROLE in GNDXGovernor) can submit a Stage 2 proposal directly, bypassing Stage 1 (Temperature Check) for routine index maintenance. They still require:

• 1,000 veGAME to submit
• Full 7-day voting period
• 66% supermajority
• Appropriate timelock

The Council bypass is for efficiency only — the community still votes.

Proposal Requirements

A valid Stage 2 proposal must include:

• The exact Solidity function call (contract address + calldata)
• Plain-language description of the action and its expected effect
• Risk assessment
• For token additions: Gaming Council research report

Vague proposals (e.g., "upgrade the contracts") without exact calldata will be rejected by the Governor.

Emergency Fast-Track

Planned — Phase 2

The emergency fast-track mechanism is fully specified but will be enabled in a future protocol upgrade. Until then, the only emergency response available is a GuardianMultisig pause (5-of-8 signers, 72-hour auto-expiry).

For market freefall scenarios requiring rapid governance action, the Gaming Council can compress the process:

• Skip Stage 1 (Temperature Check)
• Compressed Stage 2: 48-hour voting window
• Standard timelock still applies
• Requires Gaming Council proposal + community vote — no unilateral action

Governance Calendar

Event	Frequency
Gaming Council elections	Quarterly (staggered, 3–4 seats per cycle)
Index rebalance review	Quarterly
$GAME distribution to veGAME stakers	Weekly (automated)
Protocol state report	Monthly (Gaming Council)
Annual governance review	Yearly

---

See also: veGAME Mechanics · Gaming Council · Parameters