HPP DAO Voting Lifecycle

Announcements
1

Summary

This document defines the standardized Voting Lifecycle of HPP DAO, from initial discussion in the Forum to final execution.

It ensures:

  • structured governance flow

  • predictable decision-making

  • consistent proposal quality

All governance actions must follow this lifecycle.

1. Overview

HPP DAO governance follows a multi-stage process:

  • Forum Discussion

  • Proposal Formalization

  • Voting

  • Execution

  • Integration

All proposals must originate from the Forum Layer before entering the Voting Layer.

To improve clarity and discussion quality, the Forum phase is further structured into three stages:

  • General Discussion

  • Governance Topic

  • Formal Proposal

2. Forum → Voting Lifecycle

2.1 General Discussion

Purpose:

  • introduce ideas or problems

  • gather early community feedback

Characteristics:

  • non-binding

  • open participation

Duration:

  • minimum 3 days (recommended: 5 days)

Outcome:

  • direction for further discussion

  • identification of viable proposals

2.2 Governance Topic

Purpose:

  • structure a potential proposal

  • evaluate feasibility, risks, and impact

Characteristics:

  • categorized discussion (Governance / Protocol / Treasury, etc.)

  • focused stakeholder engagement

Duration:

  • minimum 5 days (recommended: 7 days)

Requirements:

  • clear problem definition

  • proposed direction

  • expected impact

Outcome:

  • decision to proceed to Formal Proposal

2.3 Formal Proposal

Purpose:

  • finalize a proposal for voting

Characteristics:

  • must follow the Proposal Template

  • proposal type must be clearly defined

Duration:

  • minimum 2-day review period before voting

Conditions:

  • prior Forum discussion completed

  • community feedback incorporated

2.4 Voting

Purpose:

  • approve or reject proposals

Method:

  • off-chain or on-chain voting

Duration:

  • standard: 5 days

Conditions:

  • Quorum: 10% of total staked HPP

  • Approval Threshold: 50% (simple majority)

Outcome:

  • Approved

  • Rejected

2.5 Execution

  • only approved proposals are executed

  • execution must strictly follow the approved scope

  • timelock may be applied depending on risk level

2.6 Integration

  • governance activities are recorded

  • participation is reflected in XP

  • data is used for rewards and analytics

3. Proposal Template

All proposals are recommended to follow the structure below:

Proposal Title

Clear and concise title

1. Summary

Brief overview of the proposal

2. Proposal Type

Protocol / Treasury / Governance / Meta

3. Problem Statement

Definition of the problem

4. Proposal Details

Detailed explanation of the proposal

5. Rationale

Justification and reasoning

6. Expected Impact

Impact on protocol, users, and risks

7. Execution Plan

How the proposal will be implemented

8. Timeline

Expected execution timeline

9. Voting Specification

  • Voting Method (Snapshot / On-chain)

  • Voting Period

  • Quorum: 10% of staked HPP

  • Approval Threshold: 50%

10. Additional Notes

References or supporting materials

4. Key Principles

  • Forum discussion is mandatory before voting

  • Governance follows a structured lifecycle

  • Voting outcomes are final and binding

  • Execution must remain deterministic and verifiable

5. Notes

This document serves as a guideline for governance participation.

Certain parameters (e.g., voting period or quorum) may evolve through future Governance Proposals.