# Why OutcomeFi

Web3 runs on **outcomes**, not just attention.

Every launch, campaign, token, and community ultimately lives or dies by whether attention converts into **real users, real usage, and real on-chain activity**. Attention is the spark. Outcomes are the fire.

Yet outcomes remain one of the least structured and least fairly rewarded inputs in the ecosystem. **OutcomeFi exists to change that.**

#### Outcomes are the real distribution layer

In crypto, distribution does not start with liquidity or listings. It starts with **who shows up, what they do, and whether it sticks**.

Outcomes determine:

* which products actually get used, not just noticed.
* which narratives convert into holders, not just impressions.
* which communities stay active past the airdrop cliff.
* which tokens build durable demand, not just launch-day hype.

But today, outcomes are fragmented across platforms, hard to attribute, and largely invisible to the teams that fund them. Attention gets measured. Outcomes mostly don't.

#### The core problem: outcomes are produced, but not attributed

Three things break the modern growth economy:

1. **Attention is easy to generate, hard to convert.** Raw impressions are abundant. Verified users, signups, wallet connects, and on-chain actions are not.
2. **Distribution lacks attribution.** Most campaigns can't tell which channel, creator, or community drove which outcome. Spend flows to noise because noise is what gets counted.
3. **Contributors are misaligned.** Creators and users generate real value, but capture little of the upside they create. Farmers dominate the leaderboards; real users get drowned out.

The result is wasted energy:

* Spam instead of signal.
* Hype instead of adoption.
* Volume instead of value.

#### OutcomeFi reframes growth as verifiable infrastructure

OutcomeFi treats growth as something that can be **attributed, verified, and rewarded**, not just observed.

At its core, OutcomeFi introduces:

* **Attribution:** which distribution channel and which contributor drove each click, signup, wallet connect, and on-chain action.
* **Verification:** integrity scoring, wallet quality checks, hold-time confirmation, and anomaly review separate real impact from bots, VPNs, and farms.
* **Qualification:** only verified outcomes count toward rewards. Empty impressions don't.
* **Incentives:** a transparent, bucket-based ledger routes value back to contributors proportionally to what they actually drove.

This turns growth from a black box into a **programmable, auditable input** that teams can design, measure, and scale.

### Buzz: the OutcomeFi execution layer

*Buzz is ChainGPT Pad's OutcomeFi layer for Web3 growth.*

It is designed to:

* give every campaign a clear objective (signups, wallet connects, on-chain actions, retention, staking share).
* attribute outcomes back to the specific contributor who drove them via **unique Buzz Links** across any platform.
* reward creators, users, and stakers through a **bucket-based ledger** (Buzz Links, Stakers, On-chain Quests, In-app Quests) plus a **Referrals overlay** that compounds real growth.
* filter out farmers, bots, and sybil clusters through layered integrity systems so budget flows to real humans.
* stay **wallet-first**: anyone can participate with just a wallet. No platform lock-in. No social account required.

Buzz does not try to own attention, it turns attention into **attributed, verifiable outcomes** and routes value back to the people who drove them.\ <br>


---

# 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/why-outcomefi.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.