# Case Studies

## Turning Creator Activity into Measurable Launch Outcomes

#### **How Web3 Teams Use Buzz to Drive Real Impact**

Buzz by ChainGPT helps Web3 teams turn community participation into measurable launch momentum. Instead of optimizing for impressions or posting volume, Buzz now rewards **verifiable outcomes** across four buckets: qualified traffic and conversions from **Buzz Links**, verified **on-chain** and **in-app quests**, proportional share for **$CGPT stakers**, and a **Referrals** overlay that compounds real growth.

Across infrastructure protocols, wallets, launch platforms, and consumer-facing Web3 products, Buzz has been used to scale distribution, attract real users, and sustain momentum well beyond launch day.

### Case in Numbers

* 20,000+ Registered Buzzers (and counting)
* 220,000+ Total Creator Posts
* $1M+ Total Reward Pool Distributed
* 2.5M+ Community Reach

#### Campaign Case Studies

Each case study below shows how different Web3 projects used Buzz to achieve specific launch goals. Context, top contributors, and measurable outcomes are included for every campaign.

{% hint style="info" %}
**Note:** The campaigns featured below were run on the earlier version of Buzz (**Buzz v1 / InfoFi**), which focused primarily on X and mindshare as the core distribution and scoring layer. They are preserved here to illustrate campaign scale and execution. The current version of Buzz has evolved into a multi-platform, outcome-based engine that rewards **qualified traffic, verified conversions, on-chain actions, in-app usage, staking share, and referrals** across any distribution channel. New v2 case studies will be added here as campaigns complete.
{% endhint %}

<figure><img src="/files/wftINg6dfuexBnfLbhUL" alt=""><figcaption></figcaption></figure>

#### Alloca ($ALLOCA) | Web3 Launch Platform

$250,000 pool · 1,666,666.66 ALLOCA · Campaign Duration: 5 Days

Alloca ran a short, high-intensity Buzz campaign to rapidly expand awareness ahead of its launch window. Within five days, the campaign activated a large base of creators and generated sustained posting activity, demonstrating Buzz’s ability to compress launch momentum into a tight timeframe.

Impact:

* 5,691 total buzzers
* 19,000+ total posts

<figure><img src="/files/E4regBYB4kTpvI4Npd0h" alt=""><figcaption></figcaption></figure>

#### Talisman ($SEEK) | AI x DeFi Wallet

$250,000 pool · 416,666.66 SEEK · Campaign Duration: 6 Days

Talisman used Buzz to support a wallet launch where credibility and consistency mattered more than one-off exposure. The campaign elevated creators with strong smart-follower ratios, helping maintain message quality while scaling reach.

Impact

* 5,433 total buzzers
* 19,000 total posts

<figure><img src="/files/1clTurN7c8biNvpLLBte" alt=""><figcaption></figcaption></figure>

#### Planck Network ($PLANCK) | Modular L1

$250,000 pool · 1,250,000 PLANCK · Campaign Duration: 7 Days

Planck Network used Buzz for targeted narrative building around its modular Layer-1 architecture. The campaign prioritized relevance over raw volume, engaging technically focused creators and analysts.

Impact

* 3,931 total buzzers
* 13,124 total posts

<figure><img src="/files/lgJsZbOdvyOdyLjknVcZ" alt=""><figcaption></figcaption></figure>

#### BitDealer ($BIT) | RWA Meme Ecosystem

$250,000 pool · 7,142,857 BIT · Campaign Duration: 21 Days

BitDealer ran a longer campaign focused on sustained engagement and high posting velocity. Buzz’s leaderboard and loyalty mechanics surfaced creators who remained active throughout the campaign rather than peaking early.

Impact

* 8,903 total buzzers
* 52,144 total posts

<figure><img src="/files/9JxYRF3Qb9RvMryOIfBp" alt=""><figcaption></figcaption></figure>

#### Snowball ($SNOWAI) | Identity and Reputation Layer

$300,000 pool · 4,000,000 SNOWAI · Campaign Duration: 77 Days

Snowball’s extended campaign focused on long-term education and reputation-building. Buzz rewarded consistent contributors over time, supporting steady discussion around identity and on-chain reputation.

Impact

* 4,012 total buzzers
* 49,900 total posts

<figure><img src="/files/1wY2SXAPII9OTm1KNK3X" alt=""><figcaption></figcaption></figure>

#### EKOX ($EKOX) | Restaking Protocol

$330,050 pool · 4,715,000 EKOX · Campaign Duration: 85 Days

EKOX ran one of the longest Buzz campaigns to date, showing Buzz’s ability to sustain creator participation over extended timelines. High smart-follower density among top contributors reinforced quality-driven distribution.

Impact

* 5,166 total buzzers
* 69,078 total posts

### What These Campaigns Demonstrate

Across different Web3 verticals and campaign lengths, Buzz consistently enables:

* Scalable creator-led distribution
* Clear attribution of impact to individual contributors
* Sustained engagement beyond launch day
* Transparent reward allocation based on measurable contribution<br>

Buzz functions as a repeatable distribution and attribution layer, giving Web3 teams a structured way to turn community activity into measurable launch outcomes. In the current v2 of Buzz, that attribution extends across any platform (via Buzz Links) and into on-chain and in-app usage, giving teams a full-funnel view of every campaign.

Ready to run your own Buzzdrop? [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/case-studies.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.
