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, replacing scattered GitHub and app-specific mappings with an on-chain source of truth.
• With ERC-7828, $ENS says the registry allows for interoperable names such as vitalik.eth@baseallowing wallets and apps to resolve cross-network identities via default $ENS flows.
• The system assigns one to each chain on.eth subdomain, uses metadata records and maintains management of the $ENS DAO while operators manage their own chain records.

What $ENS which launched this week is bigger than a naming tweak, because on.eth turns chain identity into shared infrastructure. The system introduces a canonical, $ENS-native registry for blockchain networks and their metadata, covering chains such as Base, Arbitrum and Ethereum. This matters because chain resolution data has often resided in GitHub repositories or app-specific mappings, leaving no single shared source of truth. By moving metadata within the chain $ENSthe project aims to replace distributed coordination with a verifiable naming layer that can be queried by applications. It reads like an attempt to standardize the fragmentation before it worsens.

A registry built to make cross-network names actually usable

The most direct consequence is a cleaner path to human-readable names across multiple chains. $ENS says on.eth works with ERC-7828 to support interoperable names in the format <name>@<chain>like vitalik.eth@base. Rather than inventing a separate naming system, the design extends the existing one $ENS mental models and leave the complexity to the solution flow. A wallet or application can use the $ENS name from the chain suffix, solving both $ENSand then combine the results into a single ERC-7930 interoperable address associated with a specific execution environment. That is the product promise in its simplest form.

Under the hood, the registry is designed natively $ENS plumbing instead of a bolted-on database. Each chain gets a subdomain such as zksync.on.eth, optimism.on.eth or ethereum.on.ethand those names are resolved via the on.eth Chain Resolver, which acts as both a resolver and a registry. Chain metadata is saved by default $ENS record types, including text records and binary data records. Forward resolution uses the ERC-7930 interoperable address under the interoperable-address key, while reverse.on.eth supports reverse resolution back to a human-readable chain label for customers. That architecture keeps everything familiar inside $ENS flows into wallets for developers everywhere.

Just as important, $ENS frames on.eth as a neutral coordination infrastructure, and not as private control over chain naming. The namespace emerged from interoperability discussions and was subsequently adopted by a $ENS DAO proposal and vote that left ownership of on.eth with the DAO itself. Business operations will ultimately be based on a dedicated multisig, while control over the metadata of a chain must rest with the relevant chain manager. In practical terms, $ENS seeks to reduce hardcoded mappings, improve UX across networks, and position itself as the registry layer for interoperable execution environments. That governance pitch matters.