> For the complete documentation index, see [llms.txt](https://docs.dothype.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dothype.io/quickstart/introduction-to-dothype/whats-coming-next.md).

# What's Coming Next

As we grow, we’re focused on building **structured identity,** where your name is not only an address, but also reflection of your role, reputation, and connections across the ecosystem. These are all things you can choose to opt-into as we develop the identity focused infrastructure to make your HyperEVM more seamless and secure. 

We’re ultimately expanding `.hype` into powerful tools for coordination and identity:

### 🧩 Composable Identity Layers

We're designing identity primitives that allow protocols to define and delegate structure: team namespaces, DAO roles, multi-vault operations wrapped into readable, queryable sub-identities.

### 🧠 Interoperable Metadata

Future phases will introduce contextual, role-aware metadata. Think of `.hype` names as smart containers that express what a user or entity *does*, not just who they are, that will unlock new levels of interaction, incentives, and UX focused usability across the ecosystem.

### 🔎 Legibility Across Ecosystems

We're exploring ways to surface name-linked behavior and alignment, so `.hype` becomes a trusted signal of activity, contribution, or governance standing across dashboards, bots, and smart contracts.

### 🔐 Access & Permissions Made Simple

We’re researching flexible tools that let protocols use `.hype` names to manage access, delegate permissions, and trigger actions without needing complex smart contracts.

> The future of dotHYPE is intentionally modular and composable. Our roadmap is guided by ecosystem need from the voice of the end user.

### :trophy: Leaderboard system

More details to come soon ;)

Want to help shape what’s next? Join our community → [Discord](/official-links.md)