ENS Research: Namechain, ENSIP-19 & Multichain Interop

If ENS is to realize its vision of becoming the canonical information architecture of civilization with Ethereum as the root of trust, we need a coherent framework for integrating heterogeneous trust models, lifecycles, and proof systems into a single resolvable identity space anchored in Ethereum.

The design principle is simple: Data at the edge, trust at the root.

Namespaces and data can live anywhere — across rollups, non-EVM chains, DNS, DIDs, or offchain systems — but verification and trust must always be anchored in Ethereum L1.

CCIP-Read makes this possible. Any external data source can become a verifiable edge to Ethereum if two conditions are met:

  1. A proof system exists for that source
  2. An onchain verifier can validate its proofs

I originally proposed defining a Minimal Verifier Interface (MVI), assuming a unified abstraction across all proof systems — but that puts the cart before the horse.

Logically, it should follow that we first map the design space — the trust models, proof systems, and lifecycle rules of each namespace — before defining a minimal verifier interface grounded in that reality.

Based on this research direction, I’m pleased to share that the Public Goods Working Group has awarded a grant to support this work.

That grant will be used to define the Universal Resolver Matrix (URM). In principle, the Matrix provides a taxonomy and methodology for:

  • Typing verifier/gateway patterns across ecosystems
  • Making dependencies and trust assumptions explicit
  • Systematically classifying proof systems, trust anchors, and verification needs
  • Identifying bottlenecks and missing primitives

ENSIP-19 already serves as the first modeled branch within this matrix.

It standardizes primary and reverse name resolution formats for all coin types, while defining a trustless, onchain multichain registrar and resolution process specifically for the EVM ecosystem — anchoring truth in Ethereum while enabling autonomous execution environments on L2s that share compatible primitives.

URM generalizes this architectural approach, offering a framework for analyzing and designing resolution pathways across all namespaces ENS may interact with in the future — including non-EVM chains, DNSSEC, DIDs, and offchain identity systems.

The Matrix aims to systematically map dimensions of resolution:

Dimension Question
Trust model What guarantees correctness of state?
Proof system How are those guarantees expressed?
Rules How are names are created, updated, and validated?
Verification path How is trust ultimately anchored in Ethereum?

This Matrix aims to coordinate developer and resource allocation based on a needs-first approach, and inform the DAO how to prioritize investments in resolver infrastructure, missing primitives, and standards that unlock the greatest expansion of ENS’s trust-anchored namespace coverage.

2 Likes