Ronin Governance: How Proposals and Voting Work

Ronin Governance lets RON holders decide how the Ronin treasury and ecosystem resources are used. Every idea starts as an open discussion on the Ronin Discord, moves through a RON holder review, and only then reaches a binding onchain vote.

What you can propose

• Treasury deployment: putting treasury assets to work, such as funding an initiative or allocating assets to a strategy.
• Incentive budgets: reward or incentive programs that grow activity on Ronin.
• Governance process changes: improvements to how this process works, including its thresholds, stages, or rules.
• Other: anything that genuinely needs a community decision and can be carried out if approved.

What doesn't belong here: Protocol and security-critical changes stay with validator governance. General feedback, feature requests, bug reports, and support questions also don't belong in the governance channels and may be removed as off-topic. For help with your account or a bug, contact Ronin Support.

Not sure your idea fits? Ask yourself two questions: does it need a vote, and is there something concrete someone could be authorized to do if it passes?

How it works at a glance

Phase 1: Public Temp Check

Anyone can share an idea in #public-temp-check on the Ronin Discord. You don't need to hold RON and you don't need a template. A rough idea is a perfectly good start.

1. Post your idea and explain what you want to happen.
2. Discuss it with the community and shape it based on their feedback.
3. Gather upvotes. Once your post reaches 20 upvotes from distinct accounts, you receive the @Approved Proposer role.
   
4. With that role, repost your idea as a formal proposal in Phase 2.

There is no time limit in this phase. Your idea can stay open as long as it needs to gather support, and nothing expires.

Note: The 20-upvote threshold is provisional and may change.

Phase 2: RON Holder Confirmation

In #ron-holder-confirmation, RON holders review formal proposals and decide which ones deserve an onchain vote. A proposal needs 30 upvotes to move forward.

• Who can post: members with the @Approved Proposer role, earned in Phase 1.
  
• Who can view, discuss, and upvote: members with the @RON Owner or @RON Holder role.
  

How to post a proposal

Every proposal must use the template below. A post that doesn't use it isn't treated as a proposal yet. Put the link to your original Public Temp Check thread at the top.

1. Link to Public Temp Check thread
2. Title and category: a title, plus one category (treasury deployment, incentive budget, governance process change, or other).
3. Summary: one paragraph describing the proposal.
4. Motivation: the problem, and why a vote is needed.
5. Specification: exactly what the executor is authorized to do, with amounts, assets, addresses, and ranges.
6. Cost and source of funds: which treasury balances or scheduled inflows it draws on.
7. Executor: who executes, and how.
8. Success metrics: what "worked" means, and how it will be measured.
9. Reporting: reporting cadence and what reports will contain.
10. Duration: sunset or review date.
11. Risks: what could go wrong, and the exit path.
12. Disclosures: your affiliation and any material position the proposal affects.

Tip: Once a proposal reaches 30 upvotes, the Ecosystem team checks that the template is complete, so fill in every field, especially amounts, executor, success metrics, and reporting.

Timing

• Every proposal stays open for at least 7 days.
• If it doesn't reach 30 upvotes within the 30 days after that minimum (37 days in total), it's archived.
• You can revise an archived proposal and repost it in #ron-holder-confirmation without repeating Phase 1, but upvotes start again from zero.

When a proposal passes, its upvote tally is recorded and published with the onchain vote, so anyone can verify the result after the Discord thread has scrolled away.

The Ecosystem team check

Reaching 30 upvotes shows the community wants a vote, but not yet that the proposal can be carried out. Before it goes to the voting portal, the Ronin Ecosystem team runs one narrow check and can only send a proposal back on these grounds:

Within 3 days of a proposal reaching 30 upvotes, the team posts one of three outcomes:

• Pass: the proposal moves to the onchain vote.
• Return with changes: the team lists the grounds that weren't met.
• Decline: the team names the ground and gives a written reason.

If the team doesn't respond within 3 days, the proposal passes.

If your proposal is returned: Fixes that leave the specification unchanged go straight back to the check. A material change restarts Phase 2, including the upvote count, because the original upvotes were cast on different text.

Phase 3: Onchain vote

Proposals that pass the Ecosystem team check go to a binding onchain vote, where every RON holder can take part.

1. Voting portal published: the proposal is posted on the official voting portal.
2. Snapshot: RON balances are recorded to set each wallet's voting power.
3. Vote: RON holders cast their votes.
4. End: voting closes.
5. Calculation: votes are counted against the rules below.
6. Execution: if the proposal passes, the named executor carries it out.

Frequently asked questions