# Principles

Naming in Web3 has been reduced to vanity. We believe it should be about legibility, structure, and coordination. At dotHYPE, we returned to first principles: what does identity infrastructure require in a modular, high-performance ecosystem like HyperEVM?

Our conclusions shaped every layer of our stack:

* **Modularity**: Registry, controller, and resolver are isolated components - independently upgradeable and designed to avoid monolithic bloat.
* **Composability > Coupling**: We respect ENS where it enhances interoperability, but discard legacy router patterns and static assumptions.
* **Permissionless by Default**: Access is fair, cryptographically verifiable, and free from gatekeeping.&#x20;
* **Community-Aligned**: Roadmap is shaped in partnership with builders. Feedback is and keeping a close pulse to the voice of the user is paramount.

Names in dotHYPE aims to transcend its familiar limitations. They are containers for metadata, anchors of reputation, and primitives for coordination. We believe defaults encode values. That’s why our architecture reflects a moral stance as much as a technical one: sustainability over speculation, openness over opacity, structure over chaos.

Most systems retrofitted identity into rigid models. We started clean: modular, interoperable, and extensible from day one.


---

# 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/foundations/principles.md?ask=<question>
```

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.
