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

# pUSD Rewards

**pUSD is the reward unit your Predictions referrals pay in. Separate balance, separate chart, separate Claim button.**

The Predictions Referrals page has a chart pair near the top: **Награды SOL** on the left, **Награды pUSD** on the right. They track two distinct reward streams that flow from the same referral graph but settle in different units.

## What pUSD is

* A reward unit specific to Predictions-side activity.
* Paid out separately from SOL rewards — never bundled.
* Accumulates on the page as your referrals trade prediction markets.
* Claimed via the **Забрать pUSD** button just below the chart.

The reason for the split is simple: Solana activity pays in SOL because that's the chain currency on that side; Predictions activity pays in pUSD because predictions trades quote in the platform's prediction-market unit.

## Reading the chart

The Награды pUSD chart shows your pUSD reward accrual over time. Look for:

* **Smooth growth** — your referrals are actively trading predictions.
* **Flat line** — your referrals went quiet on Predictions (they may still be active on Solana, which would show on the SOL chart).
* **Step changes** — large referrals having a single big trading session.

## Claiming pUSD

1. Reach the per-asset minimum (the button stays disabled below it).
2. Press **Забрать pUSD**.
3. The amount lands in your Wallet pUSD balance.
4. Use it directly to trade predictions, or convert to other assets if conversion is enabled in your Wallet.

The Solana side gets the same treatment for SOL — same flow, different button.

## Where pUSD lives after claiming

* In your [Wallet (Predictions)](/graphdex-docs/wallet-predictions/wallet-overview.md) balance.
* Spendable as a quote unit on the trading widget.
* History of every claim is in Wallet → Transaction History.

## Why use pUSD vs SOL

* **pUSD is purpose-built for Predictions** — no conversion friction when you spend it on prediction markets.
* **SOL is more flexible** — works across both Solana and Predictions sides, and out to external wallets.
* The choice is a function of where you want the value to live. Many predictors leave pUSD in place for their next prediction trades.

## Tier and APR boost apply equally

Both SOL and pUSD rewards are scaled by your [tier](/graphdex-docs/referrals-predictions/tiers-and-boost.md). A higher tier means a larger share of referred Predictions activity flows into your pUSD balance. The APR boost from your tier applies on the Earn side independently.

{% hint style="info" %}
The two reward charts on the Referrals page are read separately. A green SOL chart and a flat pUSD chart means your referrals are on Solana; a flat SOL chart and a green pUSD chart means they're on Predictions.
{% endhint %}

## FAQs

<details>

<summary>Can I convert pUSD into SOL or another asset?</summary>

Conversion paths are surfaced in your Wallet. The current build keeps pUSD as the native unit for Predictions; conversion options may evolve.

</details>

<details>

<summary>Does pUSD expire?</summary>

Claimed pUSD sits in your balance and does not expire. Unclaimed accrued pUSD on the Referrals page also persists until you claim.

</details>

<details>

<summary>What's the minimum to claim?</summary>

The per-asset minimum is shown in the Claim modal. The button is disabled below threshold.

</details>

<details>

<summary>If I never trade Predictions myself, can I still earn pUSD from referrals?</summary>

Yes — pUSD on Referrals depends on your referrals' Predictions activity, not your own. You will earn pUSD anytime someone in your referral tree trades a prediction.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/referrals-predictions/pusd-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.