# Arcadia DAO

## Why a DAO?

As Arcadia evolves, it is essential to ensure that the protocol becomes a sustainable, community-driven entity.

Our DAO governance structure is designed around three essential principles that foster a vibrant and resilient community: **predictability, mutual interest, and visibility.** Adhering to these pillars ensures every stakeholder has the clarity, motivation, and insight necessary to participate meaningfully.

1. **Predictability**: By clearly outlining governance rules and token distribution methods, we enable participants to anticipate how decisions are made and resources are allocated. This consistency supports steady, long-term thinking rather than reactive, short-term speculation.
2. **Mutual Interest**: Our incentive models and consensus processes encourage contributors, token holders, and builders to pursue objectives that benefit the ecosystem as a whole. When incentives are well-aligned, collaboration thrives, and the community naturally develops robust solutions.
3. **Visibility**: Transparent documentation, open discussions, and regular reporting safeguard community confidence. Shared information helps every member understand and evaluate decisions, creating a culture of accountability and constructive feedback.

Through this framework, our goal is to foster a sense of unity and shared accountability that transforms traditional “winner-takes-all” competition into collective progress.

## Timeline

Arcadia's governance will transition to a DAO model through a phased approach, empowering the community to take an increasingly active role in shaping the protocol's future.

**Phase 0 – Laying the Foundations (Completed)**

* **Focus:** Finding early signs of user demand for Arcadia. Without this, nothing else matters.
* **Achievements:** Developed a robust product, onboarded initial users, and validated the protocol’s value proposition.
* **Outcome:** A solid groundwork for community-driven growth, ensuring future governance decisions are informed by early user insights.

**Upcoming: Phase 1 – Community First**

* **Governance Evolution:**
  * Introduce community voting on non-critical decisions (e.g., feature suggestions, integrations, airdrop allocations, and contributor/grant distributions).
  * Core team retains final decision-making authority but uses community input to guide direction.
* **Initiatives:**
  * Launch community grants for non-critical development and operational tasks.
  * Begin building community trust, engagement, and alignment with the long-term vision.

**Phase 2 – Soft DAO**

* **Governance Evolution:**
  * Implement delegated voting mechanisms to strengthen community influence over the roadmap.
  * Update multisig structures to include elected community delegates, decentralizing control over treasury operations.
* **Initiatives:**
  * Community management of the DAO treasury (funding grants, partnerships, emissions, incentives, airdrops).
  * Formalize community-driven decision-making processes beyond advisory roles.

**Phase 3 – Full DAO**

* **Governance Evolution:**
  * Transition to fully on-chain governance systems, eliminating reliance on multisigs.
  * Complete decoupling of Arcadia from the founding development company, enabling self-sustaining, community-led operations.
* **Initiatives:**
  * Solidify a fully decentralized governance framework, ensuring long-term resilience and community stewardship.
  * Establish Arcadia as a fully autonomous, community-owned protocol.

***

**End State**

A mature DAO where governance, treasury management, and roadmap decisions rest entirely with the community—fostering long-term protocol stability, trust, and broad stakeholder alignment.


---

# 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.arcadia.finance/governance/arcadia-dao.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.