# What You Can Do Today ### 🔍 Reverse Resolution 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. ### ✅ Replace Your 0x Address with a Name 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 `.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. ### 🎨 **Customize Your Identity Metadata** **“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. ### 🔗 **Delegate Control Across Wallets** **“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. ### **Coming Soon in Phase 2:** * .hype-aware partner dApps * Enhanced Metadata Custimization * Community leaderboard for early holders * Embedded `.hype` lookups in HyperEVM dashboards --- # Agent Instructions: 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: ``` GET https://docs.dothype.io/quickstart/introduction-to-dothype/what-you-can-do-today.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.