> 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/inviting-users.md).

# Inviting Users

**An invite is the click. The reward is what they do afterwards.**

Inviting begins when a new user joins through your referral link. Whether that invite turns into rewardable activity depends on what the new user does after they arrive — and on the current tasks, trades, and transaction rules surfaced by the Referrals page.

{% hint style="success" %}
**Track the full funnel, not just the click**

Sign-ups are the first step; trades and on-chain activity are usually what unlock rewards. Watch both ends of the funnel.
{% endhint %}

## The Referral Event

A referral generally starts when a **new user joins through your link or invite path**. From there, rewardable activity can depend on:

* **Sign-in completion.** The invitee finishes the account flow.
* **Wallet connection.** They link a wallet to the account.
* **Trading activity.** They execute trades or other terminal actions.
* **Transaction completion.** On-chain activity tied to their account.

Referral tasks shown on the Referrals page are the source of truth — they describe what the invitee currently needs to do for activity to count.

## Referral Levels

The Referrals system has supported up to **three referral levels** at various points:

* **Level 1** — users you directly invite.
* **Level 2** — users invited by your direct referrals.
* **Level 3** — users invited by Level 2 referrals.

Levels and their reward rules depend on the current product state. **Use the live Referrals page** to confirm how levels are displayed (and rewarded) for your account today — don't rely on older descriptions.

## The User Table

Once invites land, the Referrals table surfaces each one as a row:

* **Username** — the invitee's account identifier.
* **Status** — current state of the referral.
* **Date of join** — when they signed up.
* **Earned SOL** — direct SOL rewards from their activity.
* **Earned points** — point-based rewards.
* **Earned POL / prediction-related rewards** — when available for your network or product mode.

If no referrals exist yet, the page shows an empty state with an invite prompt — a normal starting view.

## Tracking Delays

Referral activity doesn't always appear instantly. If someone used your link but doesn't show up:

* Verify the invitee actually completed sign-in.
* Check whether they've done the activity the referral task requires.
* Wait — indexing can lag, especially during high-activity windows.
* Re-check the Referrals page later.

If a known invitee still hasn't appeared after a reasonable wait, see [Tracking Referral Progress](/graphdex-docs/referrals/tracking-referral-progress.md) for the deeper audit pattern.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/a59SPBTSoTjUn3JjsVCP"><strong>Referral Link</strong></a></td><td>The link you actually share.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/smBjK7KKa5qg1hWO3uYw"><strong>Referral Rewards</strong></a></td><td>What invited activity unlocks.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/PEH8kcoGflObJH2zWUO5"><strong>Tracking Referral Progress</strong></a></td><td>Auditing the invite-to-reward funnel.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Referral-driven APR boosts also exist in [Earn](/graphdex-docs/earn-staking/rewards.md) — referral activity isn't strictly about direct rewards.
{% endhint %}

## FAQs

<details>

<summary>How do I know if someone joined through my link?</summary>

They appear as a row in the Referrals user table once their account is active and any required tasks have started. Empty-state pages mean no eligible invites yet — not necessarily that the link didn't work.

</details>

<details>

<summary>How many levels are currently rewarded?</summary>

Up to three levels have been described historically. Current rules show in your Referrals page — check there, not in older documentation.

</details>

<details>

<summary>Why isn't an invited user showing up?</summary>

Most often: they haven't completed the required activity yet (sign-in, wallet connect, trade). Indexing can also delay surface time. See \[Tracking Referral Progress]\(tracking-referral-progress.md).

</details>

<details>

<summary>Can the same invitee count twice if they sign up with different accounts?</summary>

Anti-abuse logic governs duplicate counting. Repeated sign-ups from the same person typically don't compound rewards.

</details>

<details>

<summary>Do Level 2 and Level 3 rewards happen automatically?</summary>

Yes — when the level structure is active for your account, downstream invites flow into Level 2 / 3 buckets automatically. Verify the levels on the live Referrals page.

</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/inviting-users.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.