> For the complete documentation index, see [llms.txt](https://casefun.gitbook.io/casefun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://casefun.gitbook.io/casefun/economics-and-revenue-distribution.md).

# Economics & Revenue Distribution

## 📊 Economics & Revenue Distribution Model

Unlike traditional Web3 protocols that rely on inflationary token emissions, CaseFun is built on a **Real-Yield framework**. Platform operations generate organic cash flow in native assets, which is systematically redistributed across token holders, creators, liquidity pools, and early ecosystem backers.

***

### 💰 Protocol Revenue Streams

The CaseFun Treasury captures value through five distinct, high-velocity revenue channels:

* **Case Deployment Fee:** A fixed fee of **$1.50** for every new case/token deployed on the platform.
* **Retained Campaign Volume:** The remaining percentage of case opening revenue after deducting the creator-defined Liquidity Percentage (e.g., if Liquidity Percentage is set to 90%, the remaining 10% is retained as gross platform revenue).
* **Native DEX Trading Fees:** Transaction fee cuts generated across all swap pairs on the proprietary CaseFun DEX.
* **Marketplace Commissions:** Secondary trading fees collected on all user-to-user NFT sales.
* **Enterprise Launchpad Operations:** Specialized case-launchpad fees from established Web3 projects and communities.

***

### 🔁 100% Revenue Distribution Breakdown

Every dollar generated across CaseFun's revenue streams is automatically routed through transparent smart contracts according to our **100% Community-Focused Model**:<br>

{% hint style="info" %}

100% PLATFORM REVENUE DISTRIBUTION

* 💎 25% — Buyback & Burn *(Deflationary Pressure)*
* 📈 20% — Staking Rewards *(Real Yield)*
* 🎨 20% — Creator Share *(Incentive Alignment)*
* 🏦 15% — Protocol Treasury *(Ecosystem Growth)*
* 🤝 10% — Early Investors *(Backer Loyalty)*
* 🔗 5% — Referral Engine *(Viral Growth)*
* 🎲 5% — Luck Hour Engine *(Random Liquidity)*
  {% endhint %}

| Allocation Share | Target Category        | Strategic Function & Value Driver                                                                                                                  |
| ---------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **25%**          | **$CF Buyback & Burn** | Direct open-market purchases of $CF tokens, which are permanently burned to reduce circulating supply and support long-term market capitalization. |
| **20%**          | **Staking Rewards**    | Distributed directly in native revenue assets to long-term $CF stakers.                                                                            |
| **20%**          | **Creator Share**      | Direct revenue share paid out to creators and influencers based on the gross profit of their deployed cases.                                       |
| **15%**          | **Protocol Treasury**  | Allocated for CEX listings, marketing campaigns, continuous R\&D, and operating expenses.                                                          |
| **10%**          | **Early Investors**    | Lifetime passive revenue distributions to pre-public round backers, independent of whether they hold or trade their tokens.                        |
| **5%**           | **Referral Program**   | Direct referral payouts driving affiliate traffic acquisition and community expansion.                                                             |
| **5%**           | **Luck Hour Engine**   | Daily algorithmic buyback-and-burn mechanism for community-launched tokens.                                                                        |

***

### 🎯 Creator Monetization & Key Opinion Leader (KOL) Flywheel

The **20% Creator Share** creates an unprecedented incentive model for influencers, token issuers, and crypto communities to host their trading volume on CaseFun.

#### Monetization Example:

Assume a crypto influencer or project launches a custom case with the following metrics:

* **Total Case Opening Volume:** $1,000,000
* **Configured Liquidity Percentage:** 90% ($900,000 injected straight into DEX liquidity pools)
* **Gross Retained Volume:** 10% = $100,000

$$\text{Creator Earnings} = $100,000 \times 20% = \mathbf{$20,000}$$

> **Key Takeaway:** The creator earns **$20,000 in direct revenue** from case mechanics alone, in addition to ongoing secondary DEX trading fees.

***

### 🍀 The Luck Hour Volatility Engine

To support long-tail community tokens and protect creators from post-launch price decay, CaseFun features the **Luck Hour Engine**:

1. **Daily Selection:** Every 24 hours, the protocol algorithmically selects 5 random active tokens deployed on CaseFun.
2. **Capital Allocation:** The 5% Luck Hour treasury share is split evenly among the 5 selected tokens (**1% of total daily platform revenue per token**).
3. **Instant Market Support:** This capital is automatically executed on DEXs to buy back and burn those specific community tokens.

**Impact:** Even if a community token experiences a temporary price dip, the Luck Hour mechanism creates explosive, unpredictable buy pressure, restoring market momentum and rewarding loyal holders.


---

# 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://casefun.gitbook.io/casefun/economics-and-revenue-distribution.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.
