> For the complete documentation index, see [llms.txt](https://privateness-network.gitbook.io/privateness-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privateness-network.gitbook.io/privateness-network/corenode-reward-program.md).
# Corenode Reward Program
[-> Genesis License holders, please read this segment addressing your licenses.](/privateness-network/license-acquisition-and-implementation/genesis-license-corenodes.md)
| NESS emissions | Timeframe |
| :------------: | --------------- |
| 50.000.000 | total (5 years) |
| 10.000.000 | year |
| 833.333 | month |
| 208.333 | week |
| 29.762 | day |
| 3.720 | epoch |
Payouts will be issued every 3 hours. No penalties or slashes apply if your corenode was not able to maintain >83.35% up-time of the 3h epoch.
If the up-time of your corenode is above 83.35%/epoch, your rewards will be distributed to the wallet address you have provided. The rewards are accessible immediately. We calculated 83.35% of 24 hours to allow for a total daily downtime of 4 hours. Unreliable power grids as a single point of failure should not discourage you from running a corenode.
---
# 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://privateness-network.gitbook.io/privateness-network/corenode-reward-program.md?ask=&goal=
```
`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.