# Rewards

* 25% Lumoz Token Incentive
* Potential token airdrops for the new Lumoz ecosystem chains.

## How to calculate rewards?

### Rewards of one epoch

25% of Lumoz tokens will be released over 3 years, with 95,129.37 esMOZ released per hour(one epoch). 

### Rewards of one Node(one epoch)

Each epoch, licenses across all nodes are selected based on the reward probability determined by the current [node tier](/verifier/node-tier.md). Selected licenses are eligible to participate in submissions.

The reward for each eligible license equals the current epoch’s total reward divided by the number of eligible licenses in that epoch.

The reward a node can earn equals the reward per eligible license multiplied by the number of eligible licenses within the node for the current epoch.

Node rewards will be splited 3 parts: Node commission rewards, Staking esMOZ rewards, Delegating license rewards.

### Node commission rewards(one epoch)

Node rewards multiplied by the commission rewards split.

### Staking esMOZ rewards(one epoch)

Node rewards multiplied by the Staking esMOZ split.

#### Rewards of one staker(one epoch)

The reward a staker can earn equals the total reward allocated to stakers in the current epoch, multiplied by the ratio of the staker’s stake in the node to the total stake in the node.

### Delegating esMOZ rewards(one epoch)

Node rewards multiplied by the Delegating license split.

#### Rewards of one delegator(one epoch)

The reward a delegator can earn equals the total reward allocated to delegators in the current epoch, multiplied by the ratio of the delegator’s license delegated amount to the node to the total license delegated to the node.


---

# 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.lumoz.org/verifier/verifer-node-explained/rewards.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.