# Governance and Voting (LVRX and xLVRX)

Levrex Finance aims to become a fully community-governed protocol, enabling stakeholders to influence its development and operations through a decentralized voting framework.

#### LVRX Governance Token

Governance will be facilitated through the native token **$LVRX**. Users can lock LVRX to receive **xLVRX**, which grants governance power, voting rights, and a share in protocol fee distribution.

* **2-year lock:** 1 LVRX = 1 xLVRX
* **1-year lock:** 1 LVRX = 0.5 xLVRX

xLVRX balances represent a user’s voting weight and eligibility for governance incentives.

#### Voting Mechanism

Levrex will implement an on-chain voting system with the following features:

* **Snapshot-based Voting:** Ensures fair voting by capturing balances at a specific block
* **Proposal Lifecycle:** Includes submission, discussion, and execution phases
* **Quorum Requirements:** Ensures meaningful community engagement and decision-making

#### Treasury Governance

A portion of protocol revenues and token allocations will be governed by the community treasury. xLVRX holders can vote on the use of these funds, which may include

* Liquidity incentives
* Developer grants and bounties
* Marketing and growth initiatives

#### Community Participation

Levrex invites the community to

* Engage in governance forums and Discord channels
* Submit, review, and comment on proposals
* Contribute to DAO working groups and governance upgrades

Governance empowers the Levrex ecosystem to evolve based on collective decision-making and long-term alignment. More details about xLVRX mechanics, governance rollout, and DAO transition will follow.


---

# 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.levrex.finance/guide/governance-and-voting-lvrx-and-xlvrx.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.
