Skip to main content

Proposal Process

Submitting a proposal to the GMX DAO follows a structured process, outlined below:

Phase 1: Ideation​

Phase 1 is where a proposal begins. You share your concept with the community to gather early feedback before committing to a formal document.

Post your idea on the GMX governance forum using the #idea tag. This creates a dedicated discussion thread where community members can weigh in. Many ideas also take shape informally in Discord or Telegram before a forum post is created.

If your idea gains traction, you may use Telegram polls to gauge community endorsement for the specifications you plan to include in a future Request for Comment (RFC). This soft consensus helps you understand whether your concept is ready to advance to Phase 2.

Duration: Open

Phase 2: Request for Comment​

In Phase 2, you shape your idea into a formal Request for Comment (RFC) and post it to the governance forum using the RFC template (link pending DAO approval). This invites structured community input and marks the start of the formal review process.

As you draft your RFC, incorporate community feedback and revise the proposal iteratively. The goal is to build enough endorsement to establish soft consensus, reducing the risk of rejection when the proposal advances to a formal vote.

Your RFC must follow this structure:

  • Summary
  • Motivation
  • Rationale
  • Specifications
  • Conclusion

Once your RFC has addressed the community's questions and feedback, it can advance to Phase 3.

Duration: Open

Phase 3: Snapshot Voting​

Once your RFC has built sufficient community support, it advances to a formal off-chain vote on Snapshot. Voting power is based on token balance, which gives the broader GMX community a direct voice in the outcome.

The following parameters apply:

  • Voting mechanism: Simple majority (50% + 1 of the smallest token unit)
  • Minimum tokens to submit a proposal: 10,000
  • Quorum: 50,000
  • Voting window: 5 days

If a vote passes on Snapshot but a GMX DAO delegate opposes the result, the delegate must initiate a veto proposal on Tally promptly.

Phase 4: Tally (Optional)​

Create a Tally proposal only when an on-chain transaction is required from the GMX DAO. Submit your proposal to the GMX DAO on Tally for on-chain execution.

Your proposal must include a title and a clear description of its proposed actions. The following parameters apply:

  • Voting mechanism: Qualified majority (65% + 1 of the smallest token unit)
  • Quorum: View current quorum on Tally
  • Minimum tokens to submit a proposal: 30,000
  • Voting delay: 24 hours
  • Voting window: 5 days
  • Execution delay: 24 hours

The minimum token threshold for proposing a GIP may increase depending on voter turnout and the DAO’s total voting power.

Follow-up implementations of proposals already approved on Snapshot don’t require a new Snapshot vote.

GMX DAO delegates on Tally are expected to vote “For” proposals that have already passed the Snapshot vote, unless there is a veto proposal or a particularly strong reason to vote against.