Universal Resolver 2.0 Aggregating Multiple Name Spaces in One API

As decentralized identity and Web3 naming systems proliferate across a growing number of blockchain networks and protocols, the need for interoperability has become a pressing concern. Users and developers now interact with an expanding array of domain-like systems such as Ethereum Name Service (.eth), Unstoppable Domains (.crypto, .nft, .wallet), Lens Protocol (.lens), Space ID (.bnb), and others, each operating with its own resolution logic, smart contracts, metadata structures, and underlying chain. This fragmentation presents a significant barrier to usability and integration, particularly for wallets, dApps, and browser extensions that aim to offer a seamless experience to end users. Universal Resolver 2.0 emerges in this context as a vital piece of infrastructure: a standardized API layer capable of resolving identities across multiple decentralized name spaces through a single, unified interface.

The concept of a universal resolver is not new. Early efforts, such as the Universal Resolver developed by the Decentralized Identity Foundation (DIF), focused on abstracting resolution for decentralized identifiers (DIDs), creating a framework where a DID could be mapped to its associated public keys, service endpoints, or metadata regardless of its method. However, Web3 naming systems required a different kind of resolver—one that could not only handle DID resolution but also aggregate outputs from name services that behave like DNS alternatives on the blockchain. Universal Resolver 2.0 builds on this ambition by enabling cross-name-space resolution through a modular architecture that supports pluggable resolvers for each naming system, with logic tailored to each protocol’s specifications.

At its core, Universal Resolver 2.0 offers an API endpoint where a query such as “alice.eth,” “vitalik.lens,” or “satoshi.crypto” can be submitted and resolved to a set of structured outputs. These typically include the associated wallet address, reverse record name, text records (like email, avatar, Discord, or Twitter), and potentially smart contract addresses or content hashes (such as IPFS links). The API abstracts away the complexities of calling different contracts across multiple chains, parsing their results, and formatting the output in a consistent way. For developers, this is a substantial leap forward—it allows a wallet or application to support multiple namespaces without writing custom resolution logic for each system.

The technical architecture of Universal Resolver 2.0 is designed for extensibility. Each supported namespace is implemented as a resolver module, often written to interface with the relevant smart contracts or indexers for that namespace. For ENS, the resolver module will call the ENS registry and the appropriate resolver contracts on Ethereum mainnet or Layer 2s like Optimism and Arbitrum. For Unstoppable Domains, the module may query Polygon contracts or use Unstoppable’s own resolution libraries. Lens Protocol domains involve GraphQL queries to The Graph subgraphs. Each module is isolated, enabling contributors to maintain support for one namespace without affecting others, and new namespaces can be added as adoption grows.

Importantly, Universal Resolver 2.0 is chain-agnostic. It is not limited to Ethereum and its derivatives. Support for naming systems on Solana, Cosmos, and other Layer 1s is being actively explored or developed, depending on the availability of resolution standards and read-access endpoints. In this way, the resolver becomes a unifying abstraction layer across blockchain silos, similar to how DNS translates human-readable domains into IP addresses regardless of the hosting provider or geographic location.

Security and trust minimization are also key design considerations. While some resolver modules depend on centralized APIs or proprietary endpoints (such as Unstoppable’s resolution gateway), the architecture allows developers and users to choose resolvers based on their trust assumptions. Where possible, modules use on-chain reads or decentralized indexers to minimize reliance on third parties. The output schema typically includes metadata about the resolution path, allowing applications to disclose whether the data was fetched from a fully trustless source or through a semi-centralized service.

The practical impact of Universal Resolver 2.0 is significant. For wallets, it means users can enter a human-readable name from any supported namespace and have it resolve to the correct wallet address or profile without needing to specify which protocol it belongs to. For dApps and metaverses, it simplifies the process of tagging users, rendering avatars, or linking social handles by tapping into a unified identity layer. For developers of identity verification tools or anti-sybil systems, the resolver becomes a foundational component for aggregating name-linked metadata across chains and namespaces in a standardized format.

Universal Resolver 2.0 also opens the door for new user experiences. It enables cross-name-space federation, where a user can link their .eth, .lens, and .crypto names into a composite identity that is resolved through a single query. This paves the way for rich identity composability, where a single user can own multiple namespaces but present them through a unified layer that applications can understand and interact with. It also encourages competition and diversity in the naming space, allowing new protocols to innovate without worrying about walled gardens or user confusion caused by incompatible resolution paths.

The ongoing development of Universal Resolver 2.0 involves a collaborative effort between open-source developers, identity researchers, naming protocol teams, and infrastructure providers. As Web3 moves toward a multi-chain, multi-identity future, this type of interoperability infrastructure will become indispensable. Rather than forcing convergence around a single naming standard, Universal Resolver 2.0 embraces the plurality of systems and offers a coherent way to navigate them. In doing so, it transforms Web3 naming from a fragmented landscape into a layered, navigable, and user-friendly identity environment that aligns with the decentralized ethos of the ecosystem.

As decentralized identity and Web3 naming systems proliferate across a growing number of blockchain networks and protocols, the need for interoperability has become a pressing concern. Users and developers now interact with an expanding array of domain-like systems such as Ethereum Name Service (.eth), Unstoppable Domains (.crypto, .nft, .wallet), Lens Protocol (.lens), Space ID (.bnb),…