# TD:LR

**$CHI is the convergence of meme culture and GameFi on Solana**, combining two revenue engines — Tap Game (click-to-earn) and Idle Game (passive progression) — to deliver continuous fun, a deflationary economy, and organic viral growth.

***

{% hint style="success" %}

#### **Why $CHI?**

{% endhint %}

**Zero entry barrier** → Instant access via Telegram/Web, no KYC, no complex wallets; perfect for onboarding the Web2 masses.

**Deflationary token with real utility** → Automatic burns with every tap, upgrade fees, and weekly withdrawal limits protect supply and sustain long-term value.

**Gamified and sustainable economy** → Territory NFTs, sardines as the progress currency, and strategic decisions that retain and monetize players.

**Marketing embedded in gameplay** → Public leaderboards, shareable achievements, and quests on Zealy/Galxe multiply user acquisition without paid media.

**Risk mitigation** → Audited contracts, scheduled withdrawal rules, and a cap on offline progression (6 hours) prevent dumps and inflation.

**Proven value cycle** → More players ⇒ more demand ⇒ more burning ⇒ lower supply ⇒ sustained upward price pressure.

***

**Solving the “70% failure rate” of Web3 games** by delivering real fun, a healthy economy, and instant onboarding — three often neglected essentials that unlock a potential market of **billions** of users.

***

> ***$CHI combines organic virality, a deflationary economy, and seamless Web2 onboarding, breaking through the bubble that limits most Web3 projects.***


---

# 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://whitepaper-chi.gitbook.io/docs/welcome/td-lr.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.