> For the complete documentation index, see [llms.txt](https://docs.ethena.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethena.fi/protocol-overview/governance.md).

# Governance

Rather than a flat governance structure wherein every protocol-level decision is put to a vote for participation by all governance tokenholders, the vast majority of decisions (other than those which the committees deem outside the scope of their remit) are delegated to the relevant committees described in this section. Each committee will have a clearly defined and siloed role within the broader governance framework and ecosystem.

The primary role of $ENA governance tokenholders is initially to appoint committee members on a rotating basis; however, governance going forward will be a generally iterative process where all stakeholders will adapt and tweak the system on a collective basis to move towards an efficient system that enables an appropriate balance between efficient and informed decision-making and enabling stakeholders in the community to have adequate input where it makes sense.

### Why Govern by Committee?

Due to the design of Ethena (e.g., the necessity for off-chain infrastructure), fully on-chain governance is not a practical or viable option at present. The Committee approach reflects prioritizing practicality while adding external checks and balances to that off-chain infrastructure and governance environment. 

In this framework, $ENA governance tokenholders are able to delegate everyday decision-making with respect to key aspects of the ecosystem to sophisticated, expert-level stakeholders - most of whom provide advisory and similar services to other projects and protocols in the industry - while retaining transparency during the process. In addition, the vetting process is put in place to reduce the risk of future Committee members being appointed who are ill-equipped to understand, analyze, and implement these initiatives and decisions. 

## Links

[Forum](https://gov.ethenafoundation.com/)

[Snapshot Voting](https://snapshot.org/#/ethenagovernance.eth)

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ethena.fi/protocol-overview/governance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.