> 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/bc-engine.md).

# BC Engine

<mark style="background-color:$success;">**BC Engine**</mark>**&#x20;is currently the most important mechanism-layer application for $BC. It connects $BC staking, user participation, reward distribution and supply management within one system, moving $BC from a platform reward asset into the platform's value flow system.**

<figure><img src="/files/nwJjvFNE3iUWCQ5cKCCg" alt=""><figcaption></figcaption></figure>

#### **Core Positioning**

**BC Engine** is the core mechanism layer in the BC.GAME ecosystem. It is not a single reward feature, but a value distribution system built around $BC, connecting user participation, platform rewards and long-term supply management.

#### **Mechanism Design**

After users stake $BC into BC Engine, they can participate in platform reward distribution. BC Engine runs on fixed cycles and distributes platform-related rewards to participating users, extending $BC from a one-time reward into ongoing mechanism participation.

#### **Distribution Logic**

The core role of BC Engine is to connect user behaviour, platform activity and the $BC reward mechanism. The deeper user participation becomes and the more active the platform mechanism is, the more frequently and deeply $BC circulates within the ecosystem.

#### **Burn Linkage**

BC Engine is also a core source of the daily $BC burn mechanism. Under the current mechanism design, 1% of the daily $BC flow related to BC Engine will be permanently burned.

This means the burn mechanism is not a one-off activity or an independent supply management action. It is embedded in BC Engine's daily operation. As BC Engine continues to settle and distribute rewards, $BC burns can also take place in a more continuous way.

Note: The specific calculation basis, execution timing and on-chain records for the 1% burn should be subject to the official page and on-chain data.

#### Node Network​

**BC Engine** is supported by an expanding ecosystem node network. These nodes represent different sources of platform value and ecosystem participation that can contribute to the BC Engine mechanism over time.​

Current ecosystem nodes include:​

* **🎰 BC Originals:** BC Originals represents BC.GAME's in-house game ecosystem and serves as one of the core platform-side sources connected to BC Engine.​
* ⚽️ **BETBY:** BETBY, as a sports betting technology partner, joins the BC Engine ecosystem node network and connects sports-related platform activity with the BC Engine reward mechanism.​
* **🎮 Croco Gaming:** Croco Gaming is part of the BC Engine ecosystem node network, contributing to the broader reward distribution mechanism.

#### **Ecosystem Role**

BC Engine connects three core functions of $BC:

<table><thead><tr><th width="218.140625">Function</th><th>Role</th></tr></thead><tbody><tr><td><strong>Reward Distribution</strong></td><td>Users participate in platform reward distribution by staking $BC.</td></tr><tr><td><strong>Utility Expansion</strong></td><td>$BC moves beyond a reward token and further into the platform mechanism layer.</td></tr><tr><td><strong>Supply Management</strong></td><td>1% of daily BC Engine-related $BC flow is permanently burned.</td></tr></tbody></table>

As a result, BC Engine is not only a reward product. It is the core mechanism layer in the $BC token economy, combining reward distribution, user retention and supply contraction.


---

# 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/bc-engine.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.