> For the complete documentation index, see [llms.txt](https://prodds.gitbook.io/prodds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prodds.gitbook.io/prodds/prodds-predict/fees-and-charges.md).

# Fees and Charges

Prodds maintains a clear and transparent fee structure to ensure fairness, with no hidden costs or spreads. Our platform charges two types of fees to support operational costs: the **Platform Fee** and a **Handling Fee**.

## Platform Fee

The Platform Fee is charged to winners based on the total value of the prediction pool at the close. Larger pools result in a lower fee rate for everyone. This approach encourages users to invite others, helping to reduce fees for all participants.

<details>

<summary>Platform Fee Table</summary>

```markdown
| Final Pool Size Range (in $RDM)     | Platform Fee Rate |
|-------------------------------------|-------------------|
| Final Pool Size ≤ 50K               | 5.0%              |
| 50K < Final Pool Size ≤ 100K        | 4.0%              |
| 100K < Final Pool Size ≤ 350K       | 3.5%              |
| 350K < Final Pool Size ≤ 500K       | 3.0%              |
| 500K < Final Pool Size ≤ 750K       | 2.8%              |
| 750K < Final Pool Size ≤ 1M         | 2.6%              |
| 1M < Final Pool Size ≤ 2M           | 2.4%              |
| 2M < Final Pool Size ≤ 3M           | 2.2%              |
| 3M < Final Pool Size ≤ 4M           | 2.0%              |
| 4M < Final Pool Size ≤ 5M           | 1.8%              |
| 5M < Final Pool Size ≤ 7M           | 1.6%              |
| 7M < Final Pool Size ≤ 8M           | 1.4%              |
| 8M < Final Pool Size ≤ 10M          | 1.2%              |
| 10M < Final Pool Size ≤ 20M         | 1.0%              |
| 20M < Final Pool Size ≤ 30M         | 0.9%              |
| 30M < Final Pool Size ≤ 40M         | 0.8%              |
| 40M < Final Pool Size ≤ 50M         | 0.7%              |
| 50M < Final Pool Size ≤ 75M         | 0.6%              |
| 75M < Final Pool Size ≤ 100M        | 0.5%              |
| 100M < Final Pool Size ≤ 250M       | 0.4%              |
| 250M < Final Pool Size ≤ 500M       | 0.3%              |
| 500M < Final Pool Size ≤ 1B         | 0.2%              |
| Final Pool Size > 1B                | 0.1%              |
```

</details>

{% hint style="warning" %}
The final Platform Fee rate is determined once the pool closes, meaning everyone in the pool shares the same rate based on the final pool size.
{% endhint %}

## Handling Fee

During the claim period, winnings are free to claim. After this period, unclaimed winnings will be automatically transferred to the Prodds Predict NFT holder, with a 1.99 $RDM handling fee deducted from the payout.

## Community Governance

Once the Prodds DAO is established, eligible $PRD token holders will be able to propose and vote on potential changes to the fee structure, ensuring a community-driven approach to platform improvements.


---

# 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://prodds.gitbook.io/prodds/prodds-predict/fees-and-charges.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.