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

# Roadmap

The developers are focused on the long-term vision of the project. Our goal is to provide transparent, utility-based solutions built on decentralized infrastructure. This roadmap outlines key phases to expand platform accessibility without involving financial returns or investment activities.

| Q1 2024 — Concept & Initiation Phase                             |
| ---------------------------------------------------------------- |
| <p>✅Assemble core team and project planning                      |
| <br>✅Deploy HENG token on Binance Smart Chain                    |
| <br>✅Verify smart contract and source code on BSCScan            |
| <br>✅Publish utility-based platform website (informational only) |
| <br>✅Launch official social media presence                       |
| <br>✅Initiate media communication strategy                       |
| <br>✅Publish official Whitepaper (utility token format)          |
| <br>✅Reach first 500+ token-based access participants</p>        |

| Q2–Q4 2024 — Visibility & Access Activation                                    |
| ------------------------------------------------------------------------------ |
| <p>✅ Register on decentralized conversion platforms (e.g., PancakeSwap)        |
| <br>✅ Enable token conversion via approved decentralized tools                 |
| <br>✅ Display verified project logo on BSCScan                                 |
| <br>✅ Open token-based airdrop for utility users                               |
| <br>✅ Appear in public project aggregators (e.g., Dextools)                    |
| <br>🚧 Launch token-based usage access function (non-financial)                |
| <br>🚧 Perform supply-based token halving (no return implications)             |
| <br>🚧 Community engagement goal: 5,000 users                                  |
| <br>🚧 Ecosystem growth target: 5K-10K non-financial platform access users</p> |

| Q2 2025 — Platform Feature Activation                                                                 |
| ----------------------------------------------------------------------------------------------------- |
| <p>🚧 Publish informational token visibility on external directories (e.g., CoinMarketCap, CoinGecko) |
| <br>🚧 Launch ecosystem marketplace (for access use only)                                             |
| <br>🚧 Enable platform features via token-based access                                                |
| <br>🚧 Launch mobile app with access-based activation                                                 |
| <br>🚧 Ecosystem goal: 10K–50K platform users                                                         |
| <br>🚧 Holder count target: 100K unique token participants</p>                                        |

| Q3 2026 — Utility Tool Expansion                                          |
| ------------------------------------------------------------------------- |
| <p>🚧 Expand visibility through verified informational media              |
| <br>🚧 Display project on smart wallet platforms (e.g., Trust Wallet)     |
| <br>🚧 Appear on dApp visibility sites (e.g., DappRadar)                  |
| <br>🚧 Token halving: supply adjustment only (no impact on access rights) |
| <br>🚧 Community size goal: 50K–100K                                      |
| <br>🚧 Token access user base: 100K+</p>                                  |

| Q4 2028 — Infrastructure Innovation                                                           |
| --------------------------------------------------------------------------------------------- |
| <p>🚧 Launch HENG native blockchain (for internal ecosystem use)                              |
| <br>🚧 Deploy secure wallet app for utility management                                        |
| <br>🚧 Launch AI-integrated dApp features                                                     |
| <br>🚧 Release NFT toolset for access-based usage only                                        |
| <br>🚧 Integrate third-party usage gateway (non-financial)                                    |
| <br>🚧 Enable HENG utility card (not a payment or debit card)                                 |
| <br>🚧 Final token supply halving (affects access allocations only)                           |
| <br>🚧 Final ecosystem size target: 500K utility participants (non-financial access only)</p> |

![⚠️](https://bitsmile.gitbook.io/heng-coin/~gitbook/image?url=https%3A%2F%2Fstatic.xx.fbcdn.net%2Fimages%2Femoji.php%2Fv9%2Ftdc%2F1%2F16%2F26a0.png\&width=300\&dpr=4\&quality=100\&sign=7eef40cd\&sv=2) This feature is for utility participation only. It does not offer financial returns or investment opportunities.

![⚠️](https://bitsmile.gitbook.io/heng-coin/~gitbook/image?url=https%3A%2F%2Fstatic.xx.fbcdn.net%2Fimages%2Femoji.php%2Fv9%2Ftdc%2F1%2F16%2F26a0.png\&width=300\&dpr=4\&quality=100\&sign=7eef40cd\&sv=2) Disclaimer This roadmap is for utility participation only. It does not involve financial returns, staking, trading, or investment opportunities. All features are designed solely for non-financial digital access purposes within the HENG ecosystem, with no investment value or profit expectations.


---

# 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://hengutility.gitbook.io/hengutility-docs/roadmap-and-timeline/roadmap.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.