> 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/overview/ena.md).

# ENA

ENA is the governance token of the Ethena protocol. ENA is used to govern parameters of the protocol, including the composition of USDe backing, the introduction of new backing strategies, the future allocation of protocol revenue, and the membership and remit of the Risk Committee. ENA is available across Ethereum and a number of supported chains through LayerZero, with governance accessible wherever ENA is held.

### sENA

sENA is the staked form of ENA. Holders deposit ENA into the staking contract and receive sENA, an ERC-20 token representing their position. The contract is implemented as an ERC-4626 wrapper, and unstaking is subject to a cooldown period before ENA can be withdrawn. Staking ENA into sENA signals long-term alignment with the protocol and is a route through which ENA holders participate in governance.

### Governance

Ethena governance operates through the Ethena governance forum and on-chain voting, with proposals subject to discussion, Risk Committee review where relevant, and a vote of ENA holders. The Risk Committee is a standing body responsible for setting risk parameters across the protocol - including eligibility of backing assets, exposure limits, counterparty limits, and the activation conditions for mechanisms such as the Fee Switch - and its membership is itself subject to governance.

The combination of token-holder voting, an active Risk Committee, and implementation of approved parameters allows the protocol to operate a diversified and dynamic backing portfolio while keeping decision-making transparent and subject to ENA holder oversight.

\
<https://gov.ethenafoundation.com/>

<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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ethena.fi/overview/ena.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.