# HPP DAO ### What is HPP DAO? HPP DAO is the decentralized governance body of House Party Protocol, an AI-first blockchain and data infrastructure. It makes collective decisions on protocol operations, ecosystem direction, and resource allocation, strictly through predefined rules rather than the discretion of any single entity. As the protocol matures, HPP DAO ensures that decision-making remains decentralized, stakeholder interests remain aligned, and governance outcomes remain predictable for everyone involved. *Please refer to the* [***HPP DAO Governance Framework***](https://paper.hpp.io/docs/HPP_DAO_Governance_Framework_260417.pdf) *for more information.* #### Five Core Principles


Principle	What it means
Explicitness	All procedures and authorities are defined in advance. Nothing is implied.
Predictability	Outcomes are anticipatable before participation.
Gradual Evolution	Governance evolves progressively alongside the protocol.
Accountability	Every approved decision is executable and traceable.
Least Authority	Each layer holds only the minimum power it needs to function.

#### Scope of Authority HPP DAO governs matters that affect the protocol at a systemic level. ✓ Governance rules and procedures \ ✓ Core protocol parameters \ ✓ Treasury allocation and usage \ ✓ Protocol upgrades and structural changes ✘ Individual user behavior or assets \ ✘ Management of individual applications \ ✘ Operations of external projects *\* Any authority not explicitly defined here is not implicitly granted. Ambiguous or non-executable proposals are not valid governance actions.* HPP DAO is a strategic and policy-level body. Operational execution and technical implementation are handled by operational entities, not the DAO. #### Four-Layer Architecture ``` Forum -> Voting -> Execution -> Integration ``` Forum: Entry point of governance. All proposals are discussed here before voting. Non-binding but required. Voting: Formal approval or rejection based on quorum and threshold rules. Results are final and immutable. Execution: Implements approved proposals only, within the approved scope. Timelock mechanisms apply as a safety buffer. Integration: Records participation, converts activity into XP, and feeds results into staking rewards. Does not alter governance decisions. #### Proposal Types


Type	Purpose	Binding?
Protocol	Core parameter or feature changes	✓ Yes
Treasury	Fund allocation and usage	✓ Yes
Governance	Rules and structure changes	✓ Yes
Meta	Signaling and sentiment gathering	✘ No

When a proposal spans multiple categories, it is classified by the highest level of risk or impact. ### Proposal Lifecycle No phase can be skipped. ``` Draft -> Discussion -> Formalized -> Voting -> Approved -> Executed -> Integrated -> Rejected (resubmittable with revisions) ``` ### Voting Rules * Voting Power = staked HPP tokens, fixed at snapshot before voting opens * Token movement during voting has no effect * Quorum must be met, or the proposal is automatically rejected * Approval Threshold (simple or supermajority) must be met after the Quorum is confirmed * One vote per address. Results are public and immutable. ### Execution & Timelock * No execution without prior approval * Timelock creates a mandatory delay between approval and execution * High-impact proposals carry a longer timelock; lower-risk proposals a shorter one * Execution strictly follows the approved scope and cannot be reinterpreted * Execution failure does not invalidate the original vote #### XP & Rewards Participating in governance earns XP. XP feeds into staking rewards alongside staking amount and duration. XP-eligible activities: proposal discussion, proposal submission, voting, and execution contribution. \ \* *XP does not grant voting power. It is a participation signal only.* The reward system balances capital contribution (staking) with activity contribution (XP), so governance is not purely dominated by the largest token holders. #### Forum & Communication The Forum is the only official record of governance. Discord and Telegram are supplementary. No official decision can be made outside the Forum. Posts must be clear and structured. Moderation is minimal and applied only to spam or policy violations. Forum content is a permanent governance history and cannot be deleted. #### Transparency & Accountability All of the following must be publicly verifiable: * Proposal content, discussions, and voting results * Execution outcomes, including status, target, and timestamp * XP and reward calculation criteria * All document changes with full version history Governance decisions are collectively owned by the DAO. No individual bears sole responsibility. Disputes are resolved through governance processes. ### Universal Rules * All governance changes require a Governance Proposal with a review period and non-retroactive application * Decisions made outside defined processes are not recognized as official DAO decisions * All documents must maintain a public change log \ \
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hpp.io/community/hpp-dao.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.