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

# Roadmap & Future Plans

### Planned Improvements <a href="#planned-improvements" id="planned-improvements"></a>

* **Minting Hyperliquid Names (.hl) through the Dashboard**\
  Enable users to register and mint their unique `.hl` names directly from the dashboard, fostering a stronger identity layer within the HyperEVM ecosystem.
* **Dashboard-native Alert Creation**\
  Build intuitive UI components allowing users to create, manage, and customize whale alerts and notifications without using Telegram commands.
* **Multi-platform Alert Delivery**\
  Extend alert notifications beyond Telegram to Discord, email, push notifications, and potentially other communication channels for broader accessibility.
* **Advanced Embedded Wallet Features**\
  Incorporate additional wallet functionalities such as transaction signing, portfolio management.
* **Enhanced Analytics and Visualization**\
  Develop richer data visualization tools, including real-time token flow tracking, historical trends and multi-token correlation charts.

### Scaling and Optimization Strategies <a href="#scaling-and-optimization-strategies" id="scaling-and-optimization-strategies"></a>

* Optimize database indexing, query caching, and pipeline performance to support increasing token coverage and user volume.
* Explore alternative data stores, such as ClickHouse or TimescaleDB, for better time-series analytics.
* Build modular microservices for components like alert engines and wallet management for greater scalability.

### Potential Integrations <a href="#potential-integrations" id="potential-integrations"></a>

* Integrate with on-chain governance modules to reflect voting and staking behaviors.
* Collaborate with other tools in the Hyperliquid ecosystem (e.g., Liquid Labs, GlueX Router) to expand features.
* Implement APIs for external developers to build custom analytics or bots using our indexed data.

<br>


---

# 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://hypernexus.gitbook.io/hyper-nexus/roadmap-and-future-plans.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.