# Executive Summary

$COC is a Web3 gaming token with a Viking theme, featuring a **fixed total supply of 210 billion tokens with no additional minting ever.**It's the core asset of the entire game ecosystem, powering player rewards, in-game payments, and economic circulation.Our token distribution is designed to put value directly in the hands of real users:

* **84%** of tokens go directly to players through gameplay
* **10%** allocated for liquidity establishment and maintenance
* **6%** reserved for marketing and community incentives

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

In the game, $COC isn't just a reward, it's also a payment currency. When players use $COC to purchase equipment and items, the system **periodically burns up to 36% of tokens,** creating continuous deflationary pressure.

As player numbers and game activity increase, tokens in circulation become increasingly scarce, steadily driving up value.

Additionally, all critical data related to $COC—including deposits, withdrawals, token distribution, consumption, and lottery records, are calculated and recorded through our **VWA on-chain data mechanism**. All settlements are processed automatically by the system and generate verifiable on-chain records.

Players can verify every transaction and reward themselves, ensuring the entire economic system is **transparent, verifiable, and traceable.**

**Key Highlights:**

$COC aims to build a player-driven, verifiable, and sustainable game economy. Players earn tokens through gameplay, and consumption drives deflation. On-chain data makes everything transparent, ultimately creating a fair cycle where "the more you play, the more value you gain."


---

# 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://doc.cocweb3.xyz/executive-summary.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.