> For the complete documentation index, see [llms.txt](https://docs.rivalz.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rivalz.ai/public-znode-sale/znode-rewards.md).

# zNode Rewards

Prior to the Token Generation Event (TGE), users will have the ability to choose whether to HOLD their zNodes or BURN them. Below is a breakdown of the two options:

## HOLD and BURN Options

### Option 1: HOLD the zNode 

Users who choose to HOLD their zNode and operate for the long term will benefit from:

* Total claimable tokens: 42,857 $RIZ
* Receive an extra 20% of reserved tokens fully unlocked at TGE as an Airdrop.
* The remaining allocation (35,714 $RIZ) is subject to a 2-year emission schedule.
* An additional 25% of tokens, slashed from Burned zNodes (not accounted for in the total claimable $RIZ amount).
* Access to rewards and benefits from Rivalz Alliance projects.
* Governance Participation
* Additional benefits for active validators:
  * Rewards for participating in enhancing the security of rClients and rApps.
  * Additional incentives from ADCS, ROME, Vord, and Nostrings.

{% hint style="info" %}
zNodes will become transferable 6 months after TGE.
{% endhint %}

### Option 2: BURN the zNode

{% hint style="info" %}
Note: zNode Burn is no longer available. The zNode BURN event has ended on January 25, 2025. 
{% endhint %}

Users who choose to burn their zNode before TGE will receive:

* Total Claimable Tokens: 17,857 $RIZ (50% of reserved tokens) fully unlocked at TGE.

{% hint style="warning" %}
This option disqualifies users from receiving the additional allocation reserved for the Hold Option (zNode Airdrop), any future emissions, and other benefits. 
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rivalz.ai/public-znode-sale/znode-rewards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.