TL;DR
- on.eth introduces canonical $ENS– Native registry of chains and metadata. Replace distributed GitHub and app-specific mappings with an on-chain source of truth.
- In ERC-7828, $ENS The registry is said to enable interoperable names such as
vitalik.eth@basewhich allows wallets and apps to resolve identities across networks through standards. $ENS It flows. - The system is for each chain
on.ethUse subdomains, metadata records, and maintain governance. $ENS While using DAO, operators manage their own chain records.
what $ENS What’s being released this week is more important than the name change. on.eth turns chain identity into shared infrastructure. The system introduces normalization. $ENS-A native registry of blockchain networks and their metadata, covering chains such as Base, Arbitrum, and Ethereum. This is important because chain resolution data often resides in GitHub repositories or app-specific mappings, leaving no single shared source of truth. By moving metadata on-chain $ENSthe project aims to replace distributed coordination with a verifiable naming layer that applications can query. This looks like an attempt to standardize the fragmentation before it gets worse.
A registry built to allow practical use of names across networks
The most direct result is Cleaner path to human-readable names across multiple chains. $ENS on.eth says it works with ERC-7828 to support interoperable format names vitalik.eth@base. Rather than inventing another naming system, this design extends the existing naming system. $ENS Use mental models and leave complexity to the solution flow. Can be separated by wallet or application. $ENS Name from chain suffix, resolves through both $ENSand 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, Registry is designed to be native $ENS Plumbing rather than bolt-on databases. Each chain receives a subdomain like zksync.on.eth, optimism.on.eth or ethereum.on.ethThese names are resolved through the on.eth chain resolver, which acts as both a resolver and a registry. Chain metadata is stored using the standard $ENS Record types such as text records and binary data records. Forwarding resolution uses ERC-7930 interoperable addresses. interoperable-address While holding down the key, reverse.on.eth We support reverse resolution to human-readable chain labels for our clients. Its architecture makes everything inside look familiar $ENS Developer flow across wallets everywhere.
Equally important, $ENS Rather than privately controlling chain naming, we configure on.eth as a neutral coordination infrastructure. Namespaces were born out of interoperability discussions, and then $ENS DAO proposal and vote to keep ownership of on.eth within the DAO itself. Operational management will ultimately be handled by a dedicated multisig, and control of the chain’s metadata will be handed over to the relevant chain operator. From a practical point of view, $ENS seeks to reduce hard-coded mappings, improve the overall network UX, and position itself as a registry layer for interoperable execution environments. The governance pitch is important.
