Skip to main content

DAO proposal schema

🌟 Status: Live

warning

The source of truth is the GitHub, github.com/NodeOps-app/pips.

NodeOps DAO proposal style & structure guide​

A NodeOps DAO proposal is made up of 7 sections as detailed below.

1. Proposal title​

  • Format: PIP-XX: Provide a short, clear description.
  • Style: Sentence case with only key words capitalized; avoid overly technical jargon.
  • Example: PIP-01: Establish quorum is functional

2. Summary​

A concise statement outlining the proposal’s purpose and what it aims to achieve.

3. Longer description​

A detailed explanation of the proposal, including context, background, rationale, and any relevant data or references. Clearly state the problem, the proposed solution, and why it matters for the NodeOps ecosystem.

4. Next steps​

List the concrete actions or outcomes if the proposal is approved or rejected.

Format:

  • If passed, (describe the action or change).
  • If rejected, (describe alternative or next steps).

5. Voting options​

Clearly state the required voting choices:

  • For
  • Against
  • Abstain

Provide a link to the relevant Discourse discussion thread for community input.

7. Voting window​

Set the window over which voting is possible, typically between 3 and 21 days.

Template schema​


text
Title: PIP-XX: (Short, clear description)

Summary

(One or two sentences summarizing the proposal’s intent.)

Longer Description

(Detailed rationale, context, and supporting information. Explain the problem, solution, and expected impact.)

Next Steps

- If this resolution passes, (describe the resulting action).
- If this resolution fails, (describe what will happen next).

Voting Options

- For
- Against
- Abstain

Discussion Link

(Insert forum post link).

Voting window

(Start time:date stamp to end time:date stamp inclusive).

Tips​

  • Use clear, accessible language
  • Keep sections brief but informative
  • Link to any supporting documents or references as needed

What next?​