The Ethereum Name Service (ENS) this Wednesday, March 11, launched “on.eth”, a canonical native registry on the network designed to identify blockchains and their associated metadata.
This tool enables applications and wallets Resolve network IDs Eliminate dependencies on external databases and files hosted on platforms like GitHub by directly connecting things like Base, Arbitrum, or the Ethereum main network itself.
So far, the identities of the various blockchains (known as layer 2 networks) are managed piecemeal. Each application had to maintain its own configuration map to understand which technical parameters correspond to each network.
With the advent of “on.eth”, ENS establishes shared infrastructure The information resides directly on the blockchain, allowing for automated and verifiable resolution.
Technically, this system Assign a subdomain to each network Under the “on.eth” namespace (for example, base.on.eth). Subdomains act as metadata containers, allowing you to categorize, search, and manage information more efficiently.
New mechanism for linking addresses
The information stored also includes an identifier CAP-2a unique code that identifies each network to avoid confusion. Interoperable addresses are also stored Based on ERC-7930 standardThis is an easy way to link addresses that exist on different chains, and its launch was reported by CriptoNoticias in December last year.
Simply put, Storing all this information means when your wallet interacts with the network.there is no need to query external servers and use Ethereum’s own security mechanisms to verify.
As such, ENS updates introduce the use of standards-based, interoperable names. ERC-7828adds a new human-readable format that follows the following structure: usuario.eth@red. This identifies the address as: vitalik.eth@base It specifically tells the wallet to search for the name “vitalik.eth” within the Base network environment. The software automatically separates names from network suffixes. To process transactions correctly.
The operation and management of “on.eth” is a multi-signature company (multisig), but namespace ownership remains under ENS DAO control. This governance model aims to ensure that the registry remains neutral. Works with long-term Ethereum adjustment layer.
With this release, ENS has evolved from its original role of naming user accounts to naming the entire runtime environment. The goal is to provide a logging layer that: Reduce application configuration errors multi chain It also standardizes the way users and protocols are identified across different networks.