# For Projects: Run a Buzzdrop
{% hint style="success" %}
## **TL;DR**
Buzz is a performance-based growth engine that turns distribution into **attributable outcomes**: qualified traffic, verified conversions, on-chain actions, in-app usage, and retention. Projects set growth KPIs, pick quests, plug in destinations and conversions, and pay by performance. Creators and users earn across four buckets (Buzz Links, Stakers, On-chain Quests, In-app Quests) plus a Referrals overlay. Results vary by campaign and market conditions.
{% endhint %}
### Why launches fail (and what's changed)
The market moved from hype to proof. Many launches still rely on attention spikes that don't convert into durable users or smart holders.
**The old game:**
* Big "awareness" numbers, weak lift in real users, volume, or TVL.
* Communities form late and shallow; chatter dies when rewards dry up.
* Airdrops and quests attract farmers, not users.
* Teams juggle KOL agencies, quest platforms, and spreadsheets with no single source of truth.
**The new game:**
* Rewards are tied to verifiable outcomes: wallet connects, signups, on-chain actions, product usage.
* Cross-platform attribution tracks which channels drove what.
* Integrity systems filter out bots, VPNs, and farms so budget flows to real humans.
* A single growth engine replaces fragmented tools.
Launches need to prove impact fast, and every marketing dollar needs attribution. That's what Buzz is built for.
### Buzz vs traditional KOL campaigns
| Traditional KOL campaign | Buzzdrop |
| ------------------------------- | -------------------------------------------------------------------------------------------------- |
| 20–30 KOLs negotiated 1-by-1 | Thousands of creators and users across all tiers (typical range) |
| Rate-card pricing | Rewards paid by performance: qualified clicks, conversions, verified quests, stake share |
| Flat-fee posts | Multi-platform distribution via unique Buzz Links (any channel your audience lives in) |
| Hard to attribute users/holders | Auditable points ledger + full-funnel analytics (clicks, conversions, on-chain, in-app, sentiment) |
| No loyalty loop | Loyalty engine rewards long-term supporters; farmer-resistant by design |
{% hint style="warning" %}
**Disclaimer:**
These outcomes are based on past campaigns. Buzz campaign performance varies based on vesting, project attention, reward pool size, sentiment, task design, and other factors.
{% endhint %}
### When you run a Buzzdrop, you tap into the ChainGPT engine
| Channel | Approx. reach |
| --------------------- | --------------------: |
| ChainGPT Pad X | 491K+ followers |
| ChainGPT AI X | 822K+ followers |
| ChainGPT Pad Telegram | 160K+ users |
| ChainGPT Pad Discord | 45K+ members |
| $CGPT holders | 80K+ on-chain holders |
Notable launches on ChainGPT Pad include: WalletConnect, Cookie, BubbleMaps, AITech, $CGPT, Planck, and many more.
### What you walk away with
* **Verifiable user acquisition:** signups, wallet connects, downloads, and other conversions you define.
* **On-chain growth:** verified mints, bridges, swaps (testnet), deposits/LP (with hold-time), governance participation.
* **Retention signals:** in-app usage events tied to onboarding, key features, and return-day milestones.
* **Cross-platform attribution:** which channels and which creators drove your new holders and users, at the creator level.
* **Full-funnel analytics:** qualified clicks, conversions, cost per qualified conversion, quest completion funnel, on-chain impact, fraud rate, plus mindshare and sentiment as informational layers.
* **Auditable ledger:** every point tied to a verifiable event. Export available via dashboard.
* **Post-campaign report:** before/after metrics for community growth, smart followers, and on-chain activity.
* **Fair, transparent distribution:** bucket-based snapshot with clear rules and caps.
### The Buzz reward model (what projects pay for)
Buzz v2 uses a **bucket-based reward model**. You set your reward pool and enable the buckets that fit your goals. Each bucket pays out proportionally based on verified points earned inside it.
| Bucket | Default share | What gets rewarded | Verified by |
| ----------------------- | ----------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Buzz Links** | 40% | Qualified visits + project-defined conversions (signup, wallet connect, download, etc.) | 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 exact points their referrals earn, in the same bucket | Referral edges + bucket points ledger |
Buckets and weights are **campaign-configurable**. If a bucket isn't relevant to your campaign, it can be disabled.
> **Important:** Any on-chain or in-app task that requires a payment is always **optional**. Every Buzz campaign must provide a no-cost path to participate.
#### Pick a template that matches your goal
| Template | Primary goal | Best-fit buckets | Example quests and conversions |
| ----------------------- | ---------------------------------------------- | ----------------------------------------- | ----------------------------------------------------------------------------- |
| **Activation** | Signups + wallet connects + first value moment | Buzz Links + In-app (+ optional Stakers) | Signup, wallet connect, onboarding tutorial, key feature use, return day 3 |
| **DeFi Liquidity** | TVL/LP growth with integrity controls | On-chain + Buzz Links (+ optional In-app) | Deposit/LP (hold-time), swap on testnet, stake, mint badge |
| **Testnet / Chain** | Bootstrap developer + user activity | In-app + On-chain + Buzz Links | Bridge test tokens, tx milestones, deploy contract (testnet), complete quests |
| **Community Expansion** | Community growth + referrals + retention | Buzz Links + Referrals + Stakers | Invite activated users, learning quests, join community, retention milestones |
### How a Buzzdrop works (3 steps)
#### Step 1: Campaign preparation
* **Define 1–3 growth outcomes** (e.g., signups, wallet connects, TVL, volume, usage, governance participation).
* **Pick your buckets and quests** from the task library (or request custom tasks for approval).
* **Provide your destinations** for Buzz Links: landing page, app, docs, community (Telegram/Discord), social profiles. Each destination gets a unique per-user short link.
* **Define conversions** you want to track (e.g., signup, wallet connect, download).
* **Choose a verification tier:**
* **No-dev:** quick setup using what we can observe externally.
* **Webhook:** your server pushes signed events to Buzz.
* **SDK:** you integrate an SDK for richer verification.
* **Set campaign identifiers:** required tags (hashtag, ticker, handle), content angles, and assets.
* **Lock parameters:** campaign length (2–4 weeks is typical), snapshot and claim timing aligned to your TGE or product launch.
#### Step 2: Buzzdrop goes live
Users join with **wallet + Register** (no social required). They grab their unique Buzz Links, share them anywhere your audience lives (CMC Community, Reddit, Telegram, Discord, YouTube, TikTok, Medium, Binance Square, forums, and more), complete the quests you enabled, and can stake $CGPT to earn from the Stakers bucket.
During the campaign you get:
* Real-time bucket-level leaderboards (wallet-first, outcome-based).
* A live dashboard with clicks, conversions, quest completions, and funnel conversion rates.
* Omnichannel amplification across ChainGPT's owned channels, partner networks, and KOL clusters.
* Integrity controls running continuously (bot/VPN filtering, IP/device caps, wallet scoring, hold-time checks, anomaly review).
#### Step 3: Snapshot, allocation, and post-campaign momentum
At the end of the campaign:
* The leaderboard freezes across all buckets; integrity checks sweep the ledger.
* Each bucket computes a **value-per-point** based on the total points earned inside it.
* Rewards are allocated proportionally per bucket and distributed per the campaign schedule (often with vesting).
* Loyal participants who keep supporting you after the campaign can be rewarded in future campaigns via the Loyalty Boost, reducing mercenary behavior over time.
You receive a **post-campaign report** with before/after community growth, smart follower movement, conversion funnel performance, and on-chain activity attributable to the campaign.
### Designing tasks that drive real adoption (missions)
Map each bucket to the outcomes you actually care about:
* **Buzz Links (40%) — distribution and attribution.** Define clear destinations (landing, product, app, community) and the conversions that matter (signup, wallet connect, download, custom postbacks). Creators share anywhere; you only pay for qualified traffic and verified conversions.
* **On-chain Quests (20%) — verified on-chain behavior.** Free or gasless where possible (mint a free badge, governance participation, testnet milestones), or optional paid tasks (stake, deposit/LP with hold-time, testnet swaps with caps). Always keep a free path.
* **In-app Quests (15%) — product activation and retention.** Signup, wallet connect, onboarding tutorial, key feature use, return on day 2/3/7. Verified via your webhook or SDK.
* **Stakers (25%) — ecosystem alignment.** Automatic for registered $CGPT stakers based on stake share.
* **Referrals overlay (10–20%) — organic invite loops.** Referrer earns 10–20% of the exact points their referrals earn, in the same bucket. Activation gate prevents farming.
Missions turn promoters into users. Creators who actually use your product produce better content because they can show proof and speak from experience.
### Brand safety and integrity
Buzz protects reward pools and brand trust through layered integrity controls:
* **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) that reduces rewards for fresh or suspicious wallets.
* **Hold-time verification** for deposits and LP, so points stay pending until hold periods pass.
* **Anomaly review queues** to auto-flag top earners and suspicious clusters for manual review.
* **One-level referrals** with activation gates and caps.
* **AI quality scoring** for content submitted to the Buzz Feed.
* **Content standards** you can tighten (e.g., no price talk, no financial advice).
### Setup checklist (what we need from you)
* **Narrative:** 3–5 core talking points (problem, solution, who it's for, why now).
* **Required tags:** hashtag, ticker, handle, and any campaign-specific product tags.
* **Assets:** logo kit, screenshots, optional short demo clip.
* **Buzz Links destinations:** 1–N destinations (landing, product/app, community, docs, profile).
* **Conversions to track:** the project-defined events that matter for your campaign (signup, wallet connect, download, or custom).
* **Optional quests:** 1–5 in-app and/or on-chain actions you want users to complete, with a clear UX.
* **Verification tier:** no-dev, webhook, or SDK.
* **Timeline:** campaign length, snapshot and claim timing aligned to your TGE or product launch.
* **Reward pool and split:** total pool and any adjustments to default bucket weights.
Optional: Integration notes for your dev team
Depending on the quests and conversions you enable, your team may need to support one or more of:
* **Conversion postbacks:** a signed server-to-server call when a visitor completes a conversion (e.g., signup, wallet connect, download).
* **In-app webhook events:** your server pushes signed events to Buzz when users complete in-app quests.
* **In-app pull verify:** Buzz calls your endpoint to verify completion when a user taps "Verify."
* **On-chain quests:** no integration needed in most cases, as Buzz verifies on-chain events directly from the relevant network via RPC and indexers. For custom contracts, your team may share addresses, ABIs, and event signatures.
* **SDK:** available for deeper integration where richer event metadata is helpful.
Your ChainGPT contact will share the exact integration spec for your campaign.
### We run Buzz for our own GTM
ChainGPT routes flagship GTM through Buzz (e.g., AI Hub x Buzz campaigns) to drive qualified traffic, verified product usage, and on-chain activity, using the same infrastructure offered to partners.
### Want to run a Buzzdrop?
Contact the ChainGPT Pad team with your target TGE date, budget range, and goals (qualified users, wallet connects, on-chain activity, retention, mindshare, smart followers). We'll propose a campaign plan, recommended bucket weights, and a task structure built for your outcomes.
[Let’s chat](mailto:gintare@chaingpt.org) or [book a call](https://calendly.com/buzz) and turn your launch into a cultural moment.
---
# 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/for-projects-run-a-buzzdrop.md?ask=
```
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.