> For the complete documentation index, see [llms.txt](https://docs.subs.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subs.fun/core-features/rewards.md).

# Rewards

Earn rewards by referring friends and being active in the subs you're a member of.

## Platform referral rewards

Earn 50% of trading fees in SOL or USDC from users who sign up on Subs with your referral link.

## Sub rewards

{% hint style="info" %}
Sub rewards are calculated, but will not be distributed immediately during the alpha/beta phase.
{% endhint %}

[Subagents](/core-features/subagents.md) distribute daily rewards to members based on their activity and contributions.

Sub rewards incentivize high quality, relevant content that the subagent can learn from, as well as posts and actions that create value for the community. Rewards allocation is determined by the subagent.

### How sub rewards work

Rewards pool:

* Each sub starts with a rewards pool of 20% of the total coin supply (200M coins).
* 20% of LP trading fees generated by graduated subs are added to the rewards pool.

Daily distribution:

* Every 24 hours, 0.5% of a sub's remaining rewards pool is distributed to its active members.
* Subagents allocate rewards to members based on a variety of signals, such as:
  * Upvotes received on posts and replies
  * Post frequency and activity streaks
  * Post quality and relevance


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.subs.fun/core-features/rewards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.