> For the complete documentation index, see [llms.txt](https://whitepaper.usegpu.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.usegpu.app/reward-economics/volume-scenarios.md).

# Volume Scenarios

Examine how different trading-volume assumptions change the mining pool and illustrative miner rewards over daily and monthly periods.

Trading volume is a market input to the creator-fee model. It is not controlled by USE-GPU. With fee rates unchanged, the Mining Pool changes linearly with volume.

### Scenario inputs

| Category           | Input                   |                      Value |
| ------------------ | ----------------------- | -------------------------: |
| Protocol parameter | Creator-fee rate        |                      0.30% |
| Protocol parameter | Mining allocation       | 35% of creator-fee revenue |
| Protocol parameter | Epoch duration          |                 30 minutes |
| Protocol parameter | Epochs per day          |                         48 |
| Market assumption  | Scenario A daily volume |                    $50,000 |
| Market assumption  | Scenario B daily volume |                   $200,000 |

The effective Mining Pool share is `0.105%` of trading volume:

$$
0.30% \times 35% = 0.105%
$$

This is the defined creator-fee allocation outcome. It is not an on-chain token tax.

### Pool comparison

| Metric             | $50K Daily Volume | $200K Daily Volume |
| ------------------ | ----------------: | -----------------: |
| Daily Creator Fee  |              $150 |               $600 |
| Mining Allocation  |            $52.50 |               $210 |
| Average Epoch Pool |           \~$1.09 |            \~$4.38 |
| Epochs per Day     |                48 |                 48 |

The calculation for each scenario is:

$$
\text{Daily Mining Pool} = \text{Daily Trading Volume} \times 0.30% \times 35%
$$

The `$200,000/day` scenario has four times the volume of the `$50,000/day` scenario. It therefore has four times the creator-fee revenue and four times the Mining Pool revenue, assuming the fee structure and allocation remain unchanged.

### Miner payout sensitivity

Let `X%` equal a miner's share of total Mining Power.

$$
\text{Daily Illustrative Payout} = X% \times \text{Daily Mining Pool}
$$

$$
\text{Monthly Illustrative Payout} = X% \times \text{Daily Mining Pool} \times 30
$$

| Mining Power share | $50K scenario, daily | $50K scenario, 30 days | $200K scenario, daily | $200K scenario, 30 days |
| ------------------ | -------------------: | ---------------------: | --------------------: | ----------------------: |
| `X%`               |        `X% × $52.50` |          `X% × $1,575` |           `X% × $210` |           `X% × $6,300` |

These are illustrative outputs from an assumed volume and a Mining Power share. A miner's share changes when their Mining Power or total Mining Power changes.

### Scope of the scenarios

The current numerical scenarios include creator-fee revenue only. Future GPU rental and inference services may become additional Mining Pool sources once those phases exist.

No future compute revenue is included here because the source provides no numerical assumption for it.


---

# 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://whitepaper.usegpu.app/reward-economics/volume-scenarios.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.