on.eth Launches Canonical Chain Registry, Bringing Cross-Network Identity to ENS

TL;DR

• on.eth introduces a canonical $ENS-native registry for chains and metadata, changing scattered GitHub and app-specific mappings with an on-chain supply of fact.
• With ERC-7828, $ENS says the registry permits interoperable names like vitalik.eth@base, permitting wallets and apps to resolve cross-network identities by way of normal $ENS flows.
• The system assigns every chain an on.eth subdomain, makes use of metadata information, and retains governance with the $ENS DAO whereas operators handle their very own chain information.

What $ENS launched this week is larger than a naming tweak, as a result of on.eth turns chain id into shared infrastructure. The system introduces a canonical, $ENS-native registry for blockchain networks and their metadata, masking chains comparable to Base, Arbitrum and Ethereum. That issues as a result of chain decision knowledge has usually lived in GitHub repositories or app-specific mappings, leaving no single shared supply of fact. By transferring metadata on-chain inside $ENS, the undertaking goals to interchange scattered coordination with a verifiable naming layer that functions can question. It reads like an try to standardize fragmentation earlier than it worsens.

A registry constructed to make cross-network names truly usable

Essentially the most instant consequence is a cleaner path towards human-readable names throughout a number of chains. $ENS says on.eth works with ERC-7828 to assist interoperable names within the format <identify>@<chain>, comparable to vitalik.eth@base. Reasonably than inventing a separate naming system, the design extends present $ENS psychological fashions and leaves the complexity to the decision movement. A pockets or utility can separate the $ENS identify from the chain suffix, resolve each by way of $ENS, after which mix the outcomes right into a single ERC-7930 Interoperable Handle tied to a selected execution atmosphere. That’s the product promise in easiest type.

Beneath the hood, the registry is designed as native $ENS plumbing relatively than a bolt-on database. Every chain receives a subdomain like zksync.on.eth, optimism.on.eth or ethereum.on.eth, and people names resolve by way of the on.eth Chain Resolver, which acts as each resolver and registry. Chain metadata is saved utilizing normal $ENS file varieties, together with textual content information and binary knowledge information. Ahead decision makes use of the ERC-7930 Interoperable Handle beneath the interoperable-address key, whereas reverse.on.eth helps reverse decision again to a human-readable chain label for shoppers. That structure retains every part inside acquainted $ENS flows for builders throughout wallets in all places.

Simply as vital, $ENS is framing on.eth as impartial coordination infrastructure, not personal management over chain naming. The namespace emerged from interoperability discussions, then moved by way of an $ENS DAO proposal and vote that stored possession of on.eth with the DAO itself. Operational administration will finally sit with a devoted multisig, whereas management over a sequence’s metadata is meant to be handed to the related chain operator. In sensible phrases, $ENS is attempting to cut back hardcoded mappings, enhance UX throughout networks, and place itself because the registry layer for interoperable execution environments. That governance pitch issues.