> For the complete documentation index, see [llms.txt](https://m87-gg.gitbook.io/m87-cyber-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://m87-gg.gitbook.io/m87-cyber-space/m87-cyber-space-whitepaper.md).
# M87 Cyber Space Whitepaper
**1. Introduction**
1.1 Purpose of the Document
1.2 Target Audience
1.3 How to Read the Whitepaper
1.4 Executive Summary of M87
**2. Token Fundamentals**
2.1 Emissions, Burns, and Supply Dynamics
**3. Project Overview**
3.1 The M87 Cyber Space Concept
3.2 The Hybrid Physical–Digital Model
3.3 Problem Statement – Gaps in Current Gaming & Esports Venues
3.4 The M87 Solution – Tokenized Rewards and Hybrid Economy
3.5 Strategic Vision – Thailand → Southeast Asia → Global
**4. Token Overview**
4.1 Token Identity ($M87CS)
4.2 Type, Standard, and Base Chain
4.3 Supply, Price at TGE, and Fully Diluted Valuation (FDV)
4.4 Initial Circulation Percentage
**5. Allocation & Vesting**
5.1 Allocation Overview
5.2 Vesting Mechanics
5.3 Monthly Unlock Dynamics (0–72 Months)
**6. Rewards Pool**
6.1 Purpose of the Rewards Pool
6.2 Emission Curve & Lock-at-Claim Design
6.3 Activity Scoring
6.4 Lock Multipliers
6.5 Reputation Factor
6.6 Worked Example
6.7 Anti-Abuse & Fairness Rules
6.8 Governance of Rewards Parameters
**7. Token Utility & Use Cases**
7.1 In-Venue Utility
7.2 Digital Progression & Identity
7.3 Community Governance
7.4 Integration with NFTs & Digital Assets
7.5 DeFi & Liquidity Incentives
7.6 Strategic Partnerships
7.7 Why Token Utility Matters
**8. Governance & DAO**
8.1 Governance Principles
8.2 Scope of Governance
8.3 Treasury & Reserve Oversight
8.4 Roadmap for Decentralization
8.5 Strategic Alignment
**9. Burn Mechanics**
9.1 Rationale
9.2 Automated Fee Burns
9.3 Event-Based Burns
9.4 Penalty Burns
9.5 Buybacks and Burns
**10. Technology & Infrastructure**
10.1 Smart Contract Architecture
10.2 Rewards & Identity Integration
10.3 Oracle Systems
10.4 Security & Audits
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://m87-gg.gitbook.io/m87-cyber-space/m87-cyber-space-whitepaper.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.