Your .hype name is usable the moment it’s minted.
At launch, .hype lets you choose how much (or how little) you want to share. Whether you're privacy-focused and just want a human-readable name for receiving funds, or you're building a full public identity with links, metadata, and delegation - you control what’s visible, meaningful, and connected.
Each feature you use becomes part of a larger identity graph over time to enhance discoverability, coordination, and trust - when you choose to lean into it.
Long wallet addresses are unreadable and impersonal. Sharing them feels cold—and checking them is error-prone. With .hype, your wallet becomes human:
Instead of 0x1f7a…e4A9, you send and receive using <yourname>.hype
You can reference people by name in leaderboards and dashboards if the dApp has integrated .hype resolution
“Where does this work?”
If a HyperEVM dApp supports .hype resolution, your .hype name resolves automatically.
🔍 Example: A HyperEVM explorer or DeFistaking dashboard that uses .hype resolution will display your .hype name natively instead of your wallet address.
“Why would I care about metadata?” Think of it like filling in your profile on LinkedIn or GitHub. Except this profile is onchain - portable, provable, and composable:
Add a Twitter handle, GitHub link, or bio
Set an avatar image that becomes your identity across apps
Attach a website or project link that makes it easier to find or trust you
“Why does this matter now?” Even if there aren’t rich profile pages at launch, you’re creating a discoverable surface for integrations and tools down the line. It’s your identity seed.
“Why split name and wallet?” Most people use different wallets for different things - cold storage, trading, DAO voting, etc. dotHYPE lets you:
Assign your .hype name to a secondary wallet for safety
Represent a DAO, multi-sig, or protocol with one name, while operations happen from different addresses
“What does that unlock?” This is key for teams, devs, and pseudonymous users. You stay consistent without tying everything to one key.
.hype-aware partner dApps
Enhanced Metadata Custimization
Community leaderboard for early holders
Embedded .hype lookups in HyperEVM dashboards
dotHYPE isn’t just a naming service. It’s modular identity infrastructure.
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:
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.
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.
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.
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.
More details to come soon ;)
Want to help shape what’s next? Join our community → Discord
Welcome to the future of modular on-chain identity for HyperEVM.
In Web3, we’ve built protocols for speed, liquidity, and composability - but identity is still stuck in the past. Wallets remain anonymous strings. Roles are implied, not declared. And on-chain coordination still lacks a shared, human-readable interface.
dotHYPE changes that. It’s starts with the naming service and evolves into a foundational infrastructure for how users, protocols, and agents identify and interact on HyperEVM.
Every .hype name is a container: structured to evolve, personalize, and coordinate.
This isn’t strictly just about making addresses human-readable.
It’s about making systems human-comprehensible.
dotHYPE gives you a .hype name that is:
✅ Human-readable (like you.hype)
✅ Fully on-chain and ENS-compatible
✅ Permissionless to mint
✅ Modular and programmable for expansion
Designed for today and tomorrow.
In a modular blockchain like HyperEVM, coordination happens across many contracts, dashboards, and UIs.
dotHYPE helps tie these elements together into one readable identity.
This quickstart will help you:
Let’s get started.
HyperEVM is the EVM-compatible layer of the Hyperliquid blockchain. If this is your first time exploring HyperEVM, here’s everything you need to get started.
To interact with apps and assets on HyperEVM, you’ll first need to add it to your wallet (e.g. MetaMask).
Easiest Option: Use Chainlist - one click, and you’re in.
Manual Setup: Go to your wallet > “Add Network” or “Custom RPC” and enter:
Network Name: Hyperliquid
Chain ID: 999; any other number will land to testnet
RPC URL: https://rpc.hyperliquid.xyz/evm
Currency Symbol: HYPE
Block Explorers (optional):
https://hyperevmscan.io (preferred)
Step-by-step guide to minting your .hype identity.
This guide walks you through every step of the whitelist minting process on dotHYPE.
Before you begin, make sure you’ve got:
A wallet (like MetaMask, Rabby, or Frame)
Some $HYPE on HyperEVM (You'll use $HYPE to pay for your name based on USD-pegged pricing)
A name in mind (Availability will be checked during the process)
Now that you have your .hype name, see what you can do today