> For the complete documentation index, see [llms.txt](https://cashback-eth-1.gitbook.io/cashback-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cashback-eth-1.gitbook.io/cashback-docs/why-us/rewards.md).

# Rewards

### Introduction <a href="#introduction" id="introduction"></a>

This page aims to provide a comprehensive guide on how rewards are distributed on our platform. Understanding the rewards mechanism is crucial for maximizing your benefits from participating in the platform's activities.

### Reward Distribution <a href="#reward-distribution" id="reward-distribution"></a>

The total rewards are divided into three main categories:

1. **Holding Rewards**: 50% of the total rewards.
2. **Transaction Rewards**: 40% of the total rewards.
3. **Team Fund**: 10% of the total rewards.

### Holding Rewards <a href="#holding-rewards" id="holding-rewards"></a>

When you hold CASH tokens, you are essentially participating in a reward system that allocates transactions, or shares of the reward, based on the amount of CASH you hold. The more you hold, the higher your share of the rewards.

### Maximum Holding Value <a href="#maximum-holding-value" id="maximum-holding-value"></a>

There is a maximum holding value set at 30,000 CASH, for which you will receive the maximum rewards of 1 transaction per day.

**How it Works**

1. Consider that you are earning transactions for holding CASHtokens, and every transaction counts towards your reward.
2. If 100 transactions are "created" by holding in total, 50% of the rewards will be divided among these 100 transactions.

**Example**

* **Holding 1000 CASH Tokens**:
  * In two days, you earn 0.06 transactions (TX). This is calculated as 100/30,000 = 0.03 TX per day, so for two days, it's 0.06 TX.
  * If you hold 1000 CASH for 15 days, your share is calculated as 0.03 x 15 = 0.45 TX.
* **Reward Pool Distribution**:
  * Assume the total reward pool is 10 ETH, and 50% of this (5 ETH) is for transaction rewards.
  * If there are 10 more users holding 1000 CASH for 15 days, the total transaction count is 4.5 TX. The reward per transaction is 5 ETH / 4.5 TX = 1.11 ETH per transaction.
  * With 0.45 TX, your reward would be 0.45 x 1.11 = 0.4995 ETH.

#### Transaction Rewards <a href="#transaction-rewards" id="transaction-rewards"></a>

Transaction rewards are for those who send actual transactions through the RPC URL. This accounts for 40% of the total rewards.

**How it Works**

* If 100 real transactions are sent, then the 40% of the rewards would be divided equally among these 100 transactions.

**Example**

* Let's say the 40% transaction reward pool is 40 ETH.
* If 100 real transactions are sent, each transaction would receive 40/100=0,440/100=0,4 ETH as a reward.
* So if you send 20 transactions, your reward is 20 \* 0,4 ETH = 8 ETH.

#### Team Fund <a href="#team-fund" id="team-fund"></a>

The remaining 10% of the rewards go into the team fund, which is utilized for the platform's development and maintenance.

#### Holding and Sending Transactions <a href="#holding-and-sending-transactions" id="holding-and-sending-transactions"></a>

If a user is both holding and sending real transactions, they will be eligible for rewards from both pools. This means you could earn both holding rewards and transaction rewards.


---

# 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://cashback-eth-1.gitbook.io/cashback-docs/why-us/rewards.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.