> ## Documentation Index
> Fetch the complete documentation index at: https://eketc.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Universal Resolver Matrix

> Systematic framework for mapping resolution pathways across blockchain namespaces and authentication methods

> [!NOTE]
>
> **Research Documentation**: This site presents hypothetical implementations and research concepts for the Universal Resolver Matrix framework. Content represents educational explorations and may not reflect current or planned features of Ethereum Name Service (ENS) or related protocols.

## The Universal Resolver Matrix

The **Universal Resolver Matrix (URM)** is a comprehensive framework for implementing universal name resolution across diverse namespaces and ecosystems. It provides a systematic approach to mapping resolution pathways using four core dimensions:

* **Trust Model**,
* **Proof System**,
* **Rules & Lifecycle**, and
* **Verification Path**.

Built on Ethereum Name Service (ENS) infrastructure, the URM creates a unified identity resolution system that bridges traditional DNS, blockchain ecosystems, and modern authentication methods into a single, coherent framework.

## Universal Resolution Framework

The URM implements a consistent **resolution choreography** across all namespaces through a unified four-dimensional framework:

```mermaid theme={null}
sequenceDiagram
    participant Client
    participant UniversalResolver
    participant NamespaceResolver
    participant Gateway
    participant Namespace
    participant Verifier

    Client->>+UniversalResolver: resolve(name, callData)
    UniversalResolver->>+NamespaceResolver: Route to appropriate resolver

    alt Direct Onchain Resolution
        NamespaceResolver->>NamespaceResolver: Read from contract storage
        NamespaceResolver-->>UniversalResolver: Return resolved data
    else Offchain Data Required
        NamespaceResolver->>Client: OffchainLookup(urls, callData, callback, extraData)
        Client->>+Gateway: HTTP GET/POST callData
        Gateway->>+Namespace: Query namespace-specific data
        Namespace-->>Gateway: Return raw data/proof
        Gateway->>Gateway: Construct namespace proof bundle
        Gateway-->>Client: Return proof bundle via CCIP-Read
        Client->>+NamespaceResolver: ccipCallback(proofBundle, extraData)
    end

    NamespaceResolver->>+Verifier: verify(proofBundle, query)
    Verifier->>Verifier: Validate using namespace trust model
    Verifier-->>NamespaceResolver: (valid: true, canonicalData)
    NamespaceResolver-->>UniversalResolver: Return verified result
    UniversalResolver-->>Client: Final resolution result
```

> [!NOTE]
>
> **Diagram Legend**: The conditional "alt" block shows two resolution strategies - direct onchain resolution for available data vs. CCIP-Read assisted resolution for cross-chain/namespace data fetching.

## Core Resolution Profiles

> [card] [DNSSEC Onchain Resolution](https://www.eketc.co/docs/patterns/dnssec-pattern)
>
> Trustless DNS→ENS resolution via DNSSEC P-256 signatures validated onchain.

> [card] [EVM Resolution](https://www.eketc.co/docs/patterns/evm-pattern)
>
> ENSIP-19 multichain primary names across EVM ecosystems.

> [card] [Non-EVM Resolution](https://www.eketc.co/docs/patterns/non-evm-pattern)
>
> Extends ENSIP-19 to non-EVM blockchains (Cosmos, Solana, etc.)

> [card] [WebAuthn Resolution](https://www.eketc.co/docs/patterns/webauthn-pattern)
>
> Passkey-based ENS name control and authentication.

## Framework Architecture

### Four Core Dimensions

The URM structures each resolution profile around four fundamental dimensions:

1. **Trust Model** - Establishes the cryptographic and organizational trust foundations
2. **Proof System** - Defines how proofs are generated, validated, and verified
3. **Rules & Lifecycle** - Governs the creation, management, and expiration of names
4. **Verification Path** - Maps the complete resolution pathway from query to result

### Technical Specifications

Each profile provides comprehensive technical references including:

* Contract & namespace inventory
* Deployment architecture considerations
* Edge cases and client requirements
* Implementation details and best practices

## Getting Started

**1. Choose your resolution profile**

Select the appropriate URM profile based on your target blockchain ecosystem or authentication method.

**2. Review the technical specification**

Study the complete implementation details, including trust models, proof systems, and verification paths.

**3. Implement the resolver contracts**

Deploy the required smart contracts and integrate with ENS infrastructure.

**4. Test and validate**

Ensure proper resolution across all specified pathways and handle edge cases appropriately.

## Technical Resources

> [card] [ENSIP Specifications](https://docs.ens.domains/ensip/)
>
> Official ENS Improvement Proposals and technical standards.

> [card] [EIP-7951: P-256 Precompile](https://eips.ethereum.org/EIPS/eip-7951)
>
> Ethereum precompile for P-256 elliptic curve operations.

> [card] [ENSIP-19: Multichain Names](https://docs.ens.domains/ensip/19)
>
> Primary name resolution across multiple blockchains.

> [card] [DNSSEC Algorithm 13](https://www.rfc-editor.org/rfc/rfc6605.html)
>
> P-256 ECDSA signatures for DNSSEC validation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.