# Rewards, Allocation & Claim

{% hint style="success" %}

## **TL;DR**

Buzz Points are not tokens. They're the ledger entries used to calculate allocations at snapshot. Buzz v2 uses a **bucket-based reward model**: the reward pool is split across buckets (Buzz Links, Stakers, On-chain Quests, In-app Quests), plus a Referrals overlay. At snapshot, each bucket computes a **value-per-point** and pays out proportionally to the points inside it. Integrity checks and campaign-specific caps apply.
{% endhint %}

### Buzz Points vs tokens

**Buzz Points (BP)** are ledger entries, tracked per bucket, used to:

* Rank participants on the leaderboard (overall Impact Score and per bucket).
* Calculate allocation at snapshot.

They are **not transferable**, not a token, and do not represent a guaranteed payout on their own.

**Tokens (or allocations)** are distributed based on the campaign rules after snapshot and become claimable after TGE according to the campaign's vesting schedule.

### The bucket-based reward model

Buzz v2 splits the reward pool across **four buckets** plus a **Referrals overlay**:

| Bucket                  | Default share           | What gets rewarded                                                                      | Verified by                                       |
| ----------------------- | ----------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Buzz Links**          | 40%                     | Qualified visits + project-defined conversions (e.g., signup, wallet connect, download) | Redirect + session quality + conversion postbacks |
| **$CGPT Stakers**       | 25%                     | Stake share among registered stakers (points proportional to stake)                     | Staking contract balances + campaign registration |
| **On-chain Quests**     | 20%                     | On-chain actions (mint, bridge, swap on testnet, deposit/LP with hold-time, governance) | Chain events via indexer or streams               |
| **In-app Quests**       | 15%                     | Product usage events (signup, onboarding, feature use, retention milestones)            | Project webhooks or SDK                           |
| **Referrals (overlay)** | 10–20% of earned points | Referrer earns 10–20% of the exact points their referrals earn, in the same bucket      | Referral edges + bucket points ledger             |

The default weights are **campaign-configurable**: projects can adjust bucket shares or disable buckets that don't fit their goals. Exact weights are shown on each campaign page.

You can participate in **multiple buckets** in the same campaign. Staking, sharing Buzz Links, and completing quests are all independent paths that compound into your total allocation.

### How allocation is calculated (value-per-point per bucket)

At snapshot, each bucket pays out proportionally based on the points earned inside it.

For each bucket:

```
Bucket Pool           = Total Reward Pool × Bucket Share
Value-per-point       = Bucket Pool / Total Points in Bucket
Your Bucket Reward    = Your Points in Bucket × Value-per-point
```

Your total allocation is the sum of your per-bucket rewards, plus any referral earnings (which are credited into the same buckets your referrals earned in).

#### Example: Stakers bucket (25%)

If registered stakers have **1,000,000** total staking points, and you have **100,000** staking points, you own **10%** of the Stakers bucket.

If the total reward pool is **$100,000**:

* Stakers bucket = $100,000 × 25% = **$25,000**
* Your share = $25,000 × (100,000 / 1,000,000) = **$2,500** (2.5% of the total reward pool)

The same proportional logic applies to the other buckets (Buzz Links, On-chain Quests, In-app Quests): your bucket reward is your points in that bucket divided by the total points in that bucket, times the bucket's pool.

### Referrals (10–20% overlay by bucket)

Referrals are designed to be simple and fair: the referrer earns **10–20%** of the **exact points** earned by their referred users, drawn from the **same bucket** the referral earned in.

* The referral bonus starts only after the invited user passes a minimum activation gate (e.g., registration + first quest or first qualified conversion).
* The referral bonus is calculated automatically from the points ledger and is visible in the user breakdown.
* Referrals are one-level only (no multi-tier). Campaigns can set caps on referral-derived points to reduce sybil clustering.

### Fairness and integrity controls

Buzz protects reward pools through layered controls that run continuously during the campaign and as part of the snapshot sweep:

* **Bot and data-center traffic** blocked or scored to zero.
* **VPN/proxy traffic** de-weighted or excluded per campaign strictness.
* **IP and device caps** to limit farming.
* **Wallet quality scoring** (0–100) to reduce rewards for fresh or suspicious wallets.
* **Hold-time verification** for deposits and LP: points stay pending until the hold period passes.
* **Per-task and per-bucket caps** where defined by the campaign.
* **Referral caps and activation gates.**
* **Anomaly review queues** for top earners and suspicious clusters.

Campaigns may also apply **per-user caps** or other fairness rules specific to the campaign. Exact caps are shown on the campaign page.

### Snapshot timing (how winners are determined)

After the Buzz period ends, the campaign enters **Snapshot & Allocation**. During this phase:

* Leaderboards **freeze** across all buckets.
* Only **REGISTERED** participants count.
* Integrity checks sweep the ledger (bots, VPN, duplicates, anomalies).
* Each bucket computes a **value-per-point** from its total points.
* Allocations are calculated proportionally per bucket.

### Claim timing

Claims open after TGE and follow the campaign's **vesting schedule**. Exact dates and vesting terms are defined on the campaign page. Many campaigns unlock rewards linearly over time.

### Do I need to KYC?

* **Buzzdrops:** typically **no KYC** required (geo-blocks may apply).
* **Public Sales / fundraising campaigns:** typically **KYC is required**.

Always check the specific campaign page for requirements.

### What happens if I didn't register?

If you took campaign actions (shared links, completed quests, etc.) but didn't click **Register**, you may show as **INVITE** on the leaderboard. You are **not eligible** at snapshot time unless you register before the registration window ends.

Registration requires only your **wallet**. Social accounts are optional.

### What happens to unregistered / unclaimed allocation?

Unregistered users do not receive allocation. Unclaimed or unused allocation is handled according to campaign terms (for example: redistributed, returned to the pool, or managed as stated in the campaign rules). Check the campaign page for specifics.

{% hint style="warning" %}
**Disclaimer:** Buzz campaigns are community incentive programs and do not constitute investment advice. Rewards and allocations are subject to campaign rules, eligibility requirements, integrity checks, bucket weights, caps, and vesting terms. Participation may be restricted in certain jurisdictions. Always review the campaign page for the most current terms.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.chaingpt.org/our-ecosystem/buzz-by-chaingpt/rewards-allocation-and-claim.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
