> For the complete documentation index, see [llms.txt](https://whitepaper.bc.game/bc-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.bc.game/bc-white-paper/whitepaper/token-utility-map.md).

# Token Utility Map

The utility structure of $BC will continue to deepen as the BC.GAME ecosystem develops. At present, it can be divided into three stages: Live, In Development and Planned.

#### 🔴 **Live**

<table><thead><tr><th width="230.0703125">Utility</th><th>Description</th></tr></thead><tbody><tr><td><strong>BC Engine</strong></td><td>Stake $BC into the platform's core reward engine and participate in periodic reward distribution.</td></tr><tr><td><strong>Wager Bonus</strong></td><td>Valid betting activity can accumulate $BC rewards and is currently one of the core daily acquisition paths.</td></tr><tr><td><strong>VIP Benefits System</strong></td><td>Holding and staking $BC can advance VIP level progress and unlock more platform benefits.</td></tr><tr><td><strong>Rain Community Airdrop</strong></td><td>Active users can receive instant $BC airdrops, improving community participation and return visits.</td></tr></tbody></table>

Historical distribution activities, including BC Mining Rush, Social Mining Phase 1 & 2, Solana Airdrop and 0 House Edge, have completed their phased missions. Relevant records are included in the Development History section.

#### **🔧  In Development**

<table><thead><tr><th width="229.6015625">Utility</th><th>Description</th></tr></thead><tbody><tr><td><strong>BC Engine Expansion</strong></td><td>Expand category access, with plans to include Sportsbook, Poker and other sections in the reward mechanism.</td></tr><tr><td><strong>Burn Dashboard</strong></td><td>Build an on-chain burn data dashboard to disclose burn amounts, frequency and cumulative totals.</td></tr></tbody></table>

#### 🗓️  **Planned**

<table><thead><tr><th width="229.65234375">Utility</th><th>Description</th></tr></thead><tbody><tr><td><strong>Platform Utility Expansion</strong></td><td>Embed more platform entry points, including privilege unlocking, event eligibility and fee reductions.</td></tr><tr><td><strong>Ecosystem Participation</strong></td><td>Explore access paths for $BC across the broader cross-platform ecosystem.</td></tr><tr><td><strong>Governance Expansion</strong></td><td>Advance on-chain proposals and voting mechanisms based on holdings.</td></tr><tr><td><strong>Independent Staking Layer</strong></td><td>Explore an independent staking layer outside BC Engine to strengthen long-term holding incentives.</td></tr><tr><td><strong>Access / Privilege Layer</strong></td><td>Build exclusive channels and priority benefits for high-holding users based on holdings.</td></tr><tr><td><strong>DEX Liquidity Expansion</strong></td><td>Continue to improve $BC liquidity across decentralised markets.</td></tr></tbody></table>

**$BC is more than a platform reward medium. It is the core asset structure running through platform usage, reward distribution, supply management and future ecosystem expansion.**


---

# 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:

```
GET https://whitepaper.bc.game/bc-white-paper/whitepaper/token-utility-map.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.