# 5.1 - veNEST Basics

veNEST is the governance and coordination layer of nest: it’s how long-term participants direct liquidity incentives *and* capture rewards from trading. If swaps are the fuel, veNEST is the “control panel” that decides where emissions go and fee value flows.

<figure><img src="/files/01272c899f9e53aacd0523a29eabcdf062d3a742" alt=""><figcaption></figcaption></figure>

### Key Features&#x20;

{% stepper %}
{% step %}

### Locking (Max lock duration + linear voting power)

nest uses a short, accessible vote-escrow model:

* You can lock  NEST **up to 6 months**.
* Voting power is **linear** with time:
  * **100 NEST for 6 months → 100 veNEST**
  * **100 NEST for 3 months → 50 veNEST**

A simple way to think about it:

> **veNEST ≈ NEST locked × (months remaining / 6)** (linear model).
> {% endstep %}

{% step %}

### Decay (what happens if you do nothing)

If you don’t extend or auto-max your lock, your voting power trends down toward expiry. In the current model guidance, **a max (6 month) lock left to decay reduces voting power by \~4% each epoch**.&#x20;

nest epochs run on a **weekly cycle** (votes + emissions allocation update on the epoch boundary). Once the 6-months is up your veNEST position will unlock to NEST.
{% endstep %}

{% step %}

### Voting (manual vs automated)

***

* **Route A — Manual voting:** \
  You vote each epoch to direct emissions and pursue fee value + any bribes in the pool you select\
  \
  Set up **Otomato Alerts** for vote/unlock reminders, see [**Notifications & Alerts**](/tutorials/6.10-notifications-and-alerts.md)

{% hint style="warning" %}
The last hour of voting is reserved for the **HYPE Engine Vault (HEV)** to optimally vote so APRs can vary
{% endhint %}

***

* **Route B — Automated-Voting:**\
  Deposit veNEST into the **HYPE Engine Vault (HEV)**:
  * the vault **votes automatically**
  * you receive the **MEGAHYPE distribution route** (Hype Engine rewards)&#x20;
  * rewards are compounded, buying NEST and re-locking into your veNEST position

{% hint style="warning" %}
If your veNEST is in HEV, **manual voting is disabled**, and **merge/transfer won’t work**
{% endhint %}
{% endstep %}
{% endstepper %}

### Practical links&#x20;

* Create lock: <https://app.usenest.xyz/lock/create>&#x20;
* Vote: [https://app.usenest.xyz/vote](https://app.usenest.xyz/vote?utm_source=chatgpt.com)&#x20;
* Dashboard: <https://app.usenest.xyz/dashboard>&#x20;


---

# 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.usenest.xyz/governance-venest/5.1-venest-basics.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.