> 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/overview-and-introduction.md).

# Overview & Introduction

CaseFun is a non-custodial, No-Code gamified infrastructure protocol designed for the Web3 ecosystem. It empowers brands, creators, and token communities to deploy custom, provably fair on-chain case openings, upgrades, and PvP battles.

By turning passive asset holding into interactive, high-velocity entertainment, CaseFun serves as the primary retention and utility layer for multi-chain assets, operating seamlessly across a unified Web interface and a native Telegram Mini App.

### 🎯 The Problem: The Post-Launch Utility Void

The Web3 space has mastered token *issuance*. Platforms like Pump.fun, Moonshot, and Sun.pump allow anyone to launch assets in seconds. However, the ecosystem faces a critical structural bottleneck:

* **98%+ Rapid Death Rate:** Most tokens lose over 90% of their volume, liquidity, and active holders within 48 hours post-launch due to a complete lack of ongoing utility and retention mechanics.
* **Lack of Post-Launch Tools:** Community leaders and creators have no simple, automated ways to keep holders engaged after the initial hype fades.
* **Friction in Web3 Gaming:** Traditional dApps require complex onboarding and download processes, alienating casual retail users.

***

### 💡 The Solution: CaseFun Protocol

CaseFun bridges multi-million dollar gamified cases mechanics with Web3 infrastructure. We do not compete with token issuers—we provide them with turnkey infrastructure to keep their communities active, engaged, and trading

<figure><img src="https://3846067308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXVg3TFaAQ9m2NpLh5tl%2Fuploads%2FxLGYqPc50NwTfQwne08S%2F%D0%9F%D0%B5%D1%80%D0%B2%D0%B0%D1%8F.png?alt=media&amp;token=091fdcfe-90d9-45ac-b68b-29bcf8259625" alt=""><figcaption></figcaption></figure>

#### Key Pillars:

1. **No-Code SaaS Framework.** Any project leader, creator, or community manager can deploy custom branded cases in minutes with granular operational control:
   * **Custom Win Rates & Probabilities.** Fully customizable drop rates tailored to any economic or engagement model.
   * **Flexible Token Reward Allocations.** Fully adjustable drop amounts and token volume distributions per case.
   * **Custom Visuals & Emojis.** Native integration of custom branding assets, images, or preset emoji sets for immediate visual recognition.
   * **Dynamic Pricing.** Fully configurable case opening prices and custom token pricing mechanisms.
   * **Time-Limited Campaigns.** Custom expiration timers and operational windows for limited-edition or promotional case drops.
2. **Provably Fair Protocol.** Built on transparent, verifiable randomness smart contracts, guaranteeing trustless outcomes for all participants.
3. **Cross-Platform Synchronization.** Instantaneous real-time parity between Web and Telegram Mini Apps, capturing the largest mobile Web3 user distribution channel without onboarding friction.
4. **Deflationary Ecosystem Mechanics.** Protocol fee revenues feed back into organic buyback-and-burn cycles and creator reward pools rather than inflationary emissions.


---

# 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/overview-and-introduction.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.