What is Ethereum Name Service?

Ethereum Name Service, or ENS, is a naming system built on the Ethereum blockchain. It maps human readable names like alice.eth to machine readable identifiers such as Ethereum addresses, other cryptocurrency addresses, content hashes, and metadata. If you have ever copied and pasted a long wallet address, you know how easy it is to make a typo. With ENS, you can use a name instead of a string of characters, and applications can resolve that name to the correct address. ENS is deployed on Ethereum mainnet and also on test networks. The ENS system uses dot separated hierarchical domains, similar in spirit to the internet Domain Name System, but with different architecture because it runs on Ethereum. The ENS token is used within the ENS ecosystem, including governance style activities tied to the protocol. In other words, ENS is not just a name registry, it also has a token that helps coordinate how the system evolves.

Ethereum Name Service, or ENS, is a distributed naming system based on the Ethereum blockchain. Its main job is to map human readable names like alice.eth to machine readable identifiers such as Ethereum addresses, other cryptocurrency addresses, content hashes, and metadata. Think of it as a crypto version of a domain name. Instead of relying on a central website directory, ENS uses smart contracts on Ethereum to store ownership and resolution rules. ENS also supports reverse resolution. That means an address can be linked back to a name, so applications can show a canonical name or interface description for an Ethereum address. The ENS token is part of the ENS ecosystem and is associated with governance style coordination around the protocol. In practice, people interact with ENS mainly through names, while the token is used within the ecosystem.

ENS uses dot separated hierarchical names called domains. For example, alice.eth is a name under the .eth top level domain. Top level domains like .eth and .test are owned by smart contracts called registrars. These registrar contracts define rules for how subdomains can be allocated and what it means to own a domain. If you own a domain at any level, you can configure subdomains for yourself or others. For instance, if Alice owns alice.eth, she can create pay.alice.eth and set it to resolve to the address or data she chooses. When an application needs to send funds or display an address, it can resolve the ENS name to the correct machine readable identifier. Libraries and end user applications can detect which network they are interacting with and use the ENS deployment on that network.

Send value with fewer mistakes: you can use an ENS name instead of copying a long Ethereum address. Connect addresses to other crypto data: ENS can map names to content hashes and metadata, which apps can use to display information. Improve user experience in wallets and websites: interfaces can show alice.eth rather than a raw address string. Support reverse resolution: you can associate an address with a canonical name so others can display it. Build and configure subdomains: domain owners can create subdomains like pay.alice.eth and decide what they resolve to.

The research context provided here confirms ENS is deployed on Ethereum mainnet and several test networks, and that it is based on Ethereum smart contracts. However, the context does not include specific founder names or a launch team list. Because of that, this page keeps the creator section focused on what is supported: the protocol is part of the Ethereum ecosystem and has official documentation at ens.domains. If you want to go deeper, the official docs and protocol overview can help you understand the system design and the roles of registrars and resolution contracts.

Naming model: ENS uses dot separated hierarchical domains, similar to internet domain names, but it is implemented with Ethereum smart contracts. Resolution features: ENS maps names to addresses and also supports reverse resolution, linking addresses back to names and metadata. Extensibility: ENS is described as open and extensible, so it can be used for more than just simple address lookup. Ethereum native constraints: ENS architecture is shaped by what Ethereum smart contracts can do, which differs from traditional DNS systems. Ecosystem fit: ENS is part of the Ethereum platform and is used by Ethereum based applications that want human readable identifiers.

Fewer copy paste errors: names like alice.eth are easier to read and double check than long address strings. More than addresses: ENS can map names to content hashes and metadata, so applications can attach useful information. User friendly interfaces: wallets and websites can display names, which improves clarity for new users. Ownership and rules on chain: registrar contracts and domain ownership are handled through smart contracts, which removes the need for a central registry. Compatibility with Ethereum apps: ENS is built for Ethereum deployments, and tooling can detect the network it is interacting with.

Smart contract and ecosystem risk: because ENS relies on Ethereum smart contracts, any vulnerabilities or bugs in the broader ENS components could affect resolution or ownership behavior. Network and integration risk: if an app does not support ENS resolution correctly, a name might not resolve as expected for that user. Human factors still matter: even with names, users must verify what a name resolves to, especially for payments and sensitive actions. Token market risk: ENS token price can be volatile, and token value can change even if the naming system continues to work. Regulatory uncertainty: like many crypto assets, ENS and related tokens can face changing legal interpretations in different jurisdictions.