# Community & Governance

### Community-First Approach

Stonest is built for and by its community. With 35% of the token supply dedicated to community and ecosystem development, the project is designed for broad participation and ownership.

#### Community Channels

* **Twitter / X**: Project updates, partnerships, and ecosystem news
* **Telegram**: Community discussion and real-time updates
* **Discord**: Technical discussions, developer channels, and node operator support
* **Medium**: In-depth articles, technical deep-dives, and quarterly reports

#### Governance (Phase 4)

The Stonest DAO will launch in Q1 2027, enabling token holders to participate in protocol governance:

**Governance Scope:**

* Protocol parameter adjustments (storage pricing, staking requirements)
* Treasury allocation for grants and ecosystem development
* Network upgrade proposals
* Partnership approvals for strategic integrations

**Voting Mechanism:**

* 1 token = 1 vote
* Proposals require a minimum quorum of 5% of circulating supply
* Execution follows a 48-hour timelock after vote conclusion
* Delegated voting supported for passive holders

#### Node Operator Community

Node operators form the backbone of the Stonest network. The project supports operators through:

* Comprehensive documentation and setup guides
* Dedicated Discord channels for operator support
* Performance dashboards and earnings analytics
* Regular AMAs with the core team


---

# 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://stonest.gitbook.io/stonest-docs/community-and-governance.md?ask=<question>
```

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.
