Submitting a Proposal

How DAO members propose changes, and how proposals reach a vote.

Any verified DAO member can submit a proposal. You write it in plain language and submit it through a Discord ticket. You don't need to write transactions or code: the Council turns a passed proposal into the exact transactions.

Not a member? Join the DAO, or convince a member in chat to take your idea forward. That member submits it, becomes the author and is responsible for the proposal. Tickets from anyone who is not a verified DAO member are not reviewed.

How it works

1. Submit

Open a ticket in the Monstro Discord and paste in the completed template below. The Council confirms your membership from your Discord account, so you don't need to include your wallet. Each member can have one open proposal at a time.

2. Council check

The Council reviews the proposal within 3 days. A proposal goes forward when:

  • The template is complete, and what should happen is specific enough to carry out
  • Any personal interest is disclosed: whether the author or anyone close to them benefits
  • It follows the DAO's standing rules, such as how reserve MONSTRO may be used. Changing a standing rule needs its own proposal first.
  • Payments to people or projects name what is delivered and when, and are paid in stages or as locked stakes, never as one upfront lump sum
  • It is legal and does not put DAO funds or contracts at risk

If it passes the check, the Council opens a thread for it in #governance-discussion, credited to you as the author. If not, the Council replies in your ticket with the rule it breaks, and you can fix it and resubmit. The Council does not reject a proposal because it disagrees with it. That is what the vote is for.

3. Discussion

Members have at least 3 days to ask questions and suggest changes. When the author wants to change the proposal, the Council updates the first post for them, after checking the change against the same rules.

4. Vote

The Council publishes the final text at monstrodefi.com/dao/vote, where it cannot be edited once voting opens. Voting lasts 7 days and follows the usual voting and quorum rules.

5. Execution

The Council carries out a passed proposal through the DAO multisigs within 14 days and posts every transaction in #treasury-transparency.

The Council may refuse to carry out a passed proposal only if doing so turns out to be unsafe or impossible, for example because of a risk found after the vote. It must explain why publicly.

6. Afterwards

  • A proposal that fails cannot be submitted again for 30 days, unless it has changed materially.
  • A proposal that spends DAO funds gets a short follow-up on what was delivered.

Urgent proposals

For time-sensitive items, the Council can agree to shorten discussion to 48 hours. The vote still runs 7 days.

Signal-only proposals

Proposals that ask for the DAO's opinion or direction, without any action, follow the same steps. Label them Signal only and skip the "What should happen" and "Cost" sections.

Proposal template

Copy this, fill it in and paste it into your ticket:

Title: [short name]
(The Council assigns the MIP number when it goes to a vote.)

Summary
One or two sentences: what changes if this passes.

Why
What problem this solves, or what it gains for the DAO and holders.

What should happen
In plain language, exactly what the Council should do. For example:
- "Send 500,000 MONSTRO from the emissions reserve to [wallet] as a locked stake"
- "Change staking rewards from 0.3 to 0.25 MONSTRO per second"

Cost
How much, in which tokens, and which DAO wallet pays. Write "none" if nothing.

Risks
What could go wrong, and what we would do about it.

Personal interest
Do you or anyone close to you benefit? Say how, or write "none".

Type
Executable, or Signal only.