> For the complete documentation index, see [llms.txt](https://docs.drops.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drops.co/tokens/vedop/emissions-distribution.md).

# Emissions Distribution

Intial inflationary rewards of 4500 DOP/week are set to bootstrap governance process. \
\
Upon successful governance vote 50% of interest fees can be distributed to veDOP holders in form of DOP.

### **How does rewards distribution happen?**

{% hint style="info" %}
New rewards distribution unlocks every Thursday at 00:00 UTC
{% endhint %}

Each distribution can be reffered as an Epoch that lasts 7 days. New epoch starts every Thursday at 00:00 UTC.\
User needs to remain locked for the whole epoch until rewards can be claimed for it at the start of next one.\
Example, if user locks within Epoch 1, rewards will be available at the start of Epoch 3 for Epoch 2. \
Rewards are accruing only for fully locked epochs. Lock time spent within Epoch 1, would not yield tokens. 

![Distribution example](/files/YKd9HndtEKisfcM3iRzJ)

{% hint style="info" %}
APY = weekly distribution \* 52 / total veDOP \* 100%
{% endhint %}


---

# 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.drops.co/tokens/vedop/emissions-distribution.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.