> For the complete documentation index, see [llms.txt](https://docs.glidefinance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glidefinance.io/tokenomics/glide.md).

# GLIDE Token

![](/files/-MlGx1D4muomhJ5aRrtV)

###  💠 Token Information

* Token Symbol: GLIDE
* Contract Address: `0xd39eC832FF1CaaFAb2729c76dDeac967ABcA8F27`
* Chain: Elastos Smart Chain (ESC)
* Max Supply: 50,000,000
* Farming Genesis Block: #9255555
* No pre-mint or pre-mine. Completely fair launch

### :signal\_strength: **Distribution**

| **Distributed to**  | **Allocation** | **GLIDE/block** | **GLIDE/day** |
| ------------------- | -------------- | --------------- | ------------- |
| Liquidity & Staking | 65%            | 1.462           | 25,272        |
| Community Treasury  | 22.5%          | 0.506           | 8,748         |
| Development         | 12.5%          | 0.281           | 4,860         |

![$GLIDE distribution breakdown](/files/-MlGy4gypl6bnqhFm4YM)

### ⛏️ Emission Rate

* Issuance will begin at 3 GLIDE/block (5 second block times) for a 3-month bonus period. When the bonus period ends, issuance will be cut by 25%
* After the bonus period, the token will adopt a deflationary model wherein $GLIDE issuance is cut by 15% every 6 months
* The 50,000,000 GLIDE hard cap is anticipated to take 10 years to reach

![$GLIDE token distribution rate](/files/-MlGzcJz-pAXMazkUOxQ)

| Date               | GLIDE/block | GLIDE Circulating Supply |
| ------------------ | ----------- | ------------------------ |
| November 3rd, 2021 | 3.000       | 1                        |
| February 3rd, 2022 | 2.250       | 4,730,400                |
| August 3rd, 2022   | 1.913       | 11,826,000               |
| February 3rd, 2023 | 1.626       | 17,857,260               |
| August 3rd, 2023   | 1.382       | 22,983,831               |
| February 3rd, 2024 | 1.175       | 27,341,416               |
| August 3rd, 2024   | 0.998       | 31,045,364               |
| February 3rd, 2025 | 0.849       | 34,193,719               |
| August 3rd, 2025   | 0.721       | 36,869,821               |
| February 3rd, 2026 | 0.613       | 39,144,508               |
| August 3rd, 2026   | 0.521       | 41,077,992               |
| February 3rd, 2027 | 0.443       | 42,721,453               |
| August 3rd, 2027   | 0.377       | 44,118,395               |
| February 3rd, 2028 | 0.320       | 45,305,796               |
| August 3rd, 2028   | 0.272       | 46,315,087               |
| February 3rd, 2029 | 0.231       | 47,172,984               |
| August 3rd, 2029   | 0.197       | 47,902,196               |
| February 3rd, 2030 | 0.167       | 48,522,027               |
| August 3rd, 2030   | 0.142       | 49,048,883               |
| February 3rd, 2031 | 0.121       | 49,496,710               |
| August 3rd, 2031   | 0.103       | 49,877,364               |
| October 12th, 2031 | 0.000       | 50,000,000               |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.glidefinance.io/tokenomics/glide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.