> For the complete documentation index, see [llms.txt](https://docs.thenile.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thenile.exchange/introduction-to-nile/ve-3-3-fundamentals/venile-venft/venile-revenue-distribution-schedule.md).

# veNILE Revenue Distribution Schedule

{% hint style="info" %}
During epoch 0, since there was no pre-voting, all trading fees will be rolled into Epoch 1.
{% endhint %}

**Vote Bribes:** Users earn vote bribes immediately after the epoch flips. If there is a 1000 USDC bribe on a pair, and you are the only voter, you will receive 1000 USDC claimable at Thursday 0 UTC.

**Swap Fees:** Voters earn trading fees in real-time throughout the week, based on the pool(s) they voted for before the epoch flips. These are pushed on a regular cadence permissionlessly when the fee threshhold is achieved.


---

# 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.thenile.exchange/introduction-to-nile/ve-3-3-fundamentals/venile-venft/venile-revenue-distribution-schedule.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.