> 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/burn-mechanism.md).

# Burn Mechanism

BC.GAME connects the continuous operation of BC Engine with $BC supply management through a daily burn mechanism. Under the current mechanism design, if users unstake $BC that has been staked for less than seven days, 1% of the unstaked amount will enter the burn process.

#### **Short-Term Unstake Burn**

After users stake $BC into BC Engine, if that portion of $BC is unstaked before it has been staked for seven days, the system will route 1% of the unstaked amount into the burn process.

This mechanism is not a one-off burn event. It is directly tied to the BC Engine staking cycle and user actions. It encourages more stable staking behaviour while giving short-cycle unlocking a clear supply management effect.

*\*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.*

#### **Transparency**

All burn operations should be executed on-chain, and each record should be independently searchable and verifiable. The platform will continue to disclose burn amounts, execution times and cumulative totals to help users track changes in $BC supply.

Historical burn records: to be added, including the 250 million $BC Social Mining Phase 2 burn and other records.

#### **Why It Matters**

After users stake $BC into BC Engine, if that portion of $BC is unstaked before it has been staked for seven days, the system will route 1% of the unstaked amount into the burn process.

This mechanism is not a one-off burn event. It is directly tied to the BC Engine staking cycle and user actions. It encourages more stable staking behaviour while giving short-cycle unlocking a clear supply management effect.

For holders, the key point of this mechanism is verifiability: the burn is not a verbal commitment, but an on-chain execution record that can be continuously tracked.

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


---

# 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/burn-mechanism.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.