Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

ENS (Ethereum Name Service)

A decentralized naming system that maps human-readable names (like alice.eth) to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.
Chainscore © 2026
definition
BLOCKCHAIN DOMAIN SYSTEM

What is ENS (Ethereum Name Service)?

ENS is a decentralized naming service that maps human-readable names to machine-readable identifiers on the Ethereum blockchain and beyond.

The Ethereum Name Service (ENS) is a distributed, open, and extensible naming system built on the Ethereum blockchain. Its core function is to translate human-friendly names like alice.eth into machine-readable identifiers such as Ethereum addresses, other cryptocurrency addresses, content hashes, and metadata. This system operates similarly to the internet's Domain Name Service (DNS) but for blockchain resources, replacing complex hexadecimal strings with memorable names to improve user experience and reduce errors in transactions.

Technically, ENS is a set of smart contracts on the Ethereum mainnet. The registry is the central contract that maintains a list of all domains and subdomains, recording the owner, resolver, and time-to-live for each record. A resolver is a separate contract that translates names into the specific resource they point to, such as an address or IPFS hash. Names are represented as Non-Fungible Tokens (NFTs), meaning ownership of a .eth domain is a transferable digital asset managed by the owner's crypto wallet.

The primary use case for ENS is simplifying cryptocurrency transactions. Instead of copying a long public address like 0x4cbe58c50480..., users can simply send funds to wallet.eth. However, its utility extends far beyond this. ENS supports multi-chain addresses, allowing a single name to resolve to addresses on chains like Bitcoin, Solana, or Layer 2 networks. It can also point to decentralized website content (via IPFS or Arweave hashes), store profile metadata like avatars and social handles, and function as a universal username across decentralized applications.

Acquiring an ENS name involves registering it through the official ENS app or a supported marketplace. Names are registered via a Vickrey auction-inspired process for a minimum of one year, with annual renewal fees paid in ETH. The decentralized governance of the ENS protocol is managed by ENS DAO, where token holders vote on treasury management, protocol upgrades, and the integration of new features, ensuring the service evolves in a community-driven manner.

how-it-works
TECHNICAL OVERVIEW

How Does ENS Work?

The Ethereum Name Service (ENS) is a decentralized, open-source naming system built on the Ethereum blockchain that maps human-readable names like `alice.eth` to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.

At its core, ENS operates as a two-layer system built from smart contracts. The first layer is the ENS Registry, a single, central contract that maintains a record of all domains and subdomains. For each name, the registry stores three critical pieces of information: the owner (an Ethereum address or smart contract), the resolver for that name, and the time-to-live (TTL) for cached records. The owner has exclusive rights to modify these records and create subdomains, establishing a clear hierarchy and ownership model.

The second critical component is the Resolver. A resolver is a smart contract specified in the registry that translates a name into the actual resource it points to, such as a cryptocurrency address (like 0x...), an IPFS content hash, or an off-chain text record (e.g., an avatar URL or email). When an application needs to resolve alice.eth, it queries the Registry for the associated resolver address, then queries that resolver contract for the specific record type requested. This separation of the registry and resolver logic allows for flexibility and upgradability in how records are managed.

Name registration and renewal are governed by a Vickrey auction-inspired process for .eth names, though it now functions as a straightforward rent system. Users register a name by committing to the network, revealing their intent, and then paying an annual fee based on the name's length (e.g., 5+ character names cost $5/year in ETH). This fee is paid to the ENS DAO treasury, funding ongoing protocol development. Registrations are managed via the NameWrapper contract, which tokenizes ENS names as ERC-1155 NFTs, making them easily tradable on marketplaces and composable within other DeFi applications.

Beyond simple address resolution, ENS supports multichain interoperability through cross-chain resolvers and the CCIP-Read standard. This allows an ENS name registered on Ethereum to resolve to addresses on other blockchains like Bitcoin, Litecoin, or Layer 2 networks. Furthermore, ENS enables decentralized websites by resolving names to InterPlanetary File System (IPFS) or Swarm content hashes, creating censorship-resistant web hosting. These advanced features demonstrate ENS's evolution from a simple address translator into a foundational protocol for decentralized identity and resource mapping.

key-features
CORE MECHANICS

Key Features of ENS

The Ethereum Name Service (ENS) is a distributed, open, and extensible naming system built on the Ethereum blockchain. It maps human-readable names like alice.eth to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.

01

Human-Readable Address Resolution

ENS primarily maps human-readable domain names (e.g., vitalik.eth) to cryptographic identifiers like Ethereum addresses, Bitcoin addresses, or IPFS content hashes. This eliminates the need to copy and paste long, error-prone hexadecimal strings. The resolution process is performed by querying the ENS registry and the relevant resolver smart contract on-chain.

02

Decentralized Ownership & Management

ENS names are non-fungible tokens (NFTs) compliant with the ERC-721 standard. Ownership is recorded on the Ethereum blockchain, giving the holder complete, verifiable control. Owners can:

  • Transfer the name to another wallet.
  • Set and update resolver contracts.
  • Manage subdomains (e.g., pay.alice.eth).
  • Configure records for the name (address, avatar, text).
03

Multi-Chain & Multi-Coin Support

An ENS name is not limited to Ethereum. Through its resolver system, a single name can point to addresses on many different blockchains. Standardized address record types exist for:

  • Ethereum (ETH)
  • Bitcoin (BTC)
  • Litecoin (LTC)
  • Dogecoin (DOGE)
  • And many others via the CoinType standard (SLIP-44).
04

Decentralized Naming Hierarchy

ENS uses a hierarchical domain system like DNS, but managed on-chain. The root node is controlled by a multi-signature contract. Top-level domains (TLDs) like .eth are managed by smart contracts (registrars). Anyone can create subdomains for a name they own (e.g., blog.alice.eth), enabling decentralized organizational structures and application-specific addresses.

05

Integrated Profile & Metadata (Text Records)

Beyond addresses, ENS supports storing arbitrary text records, allowing names to function as decentralized profiles. Common standardized record types include:

  • Avatar (avatar): URL for a profile picture (often an NFT).
  • Description (description): Bio or description text.
  • URL (url): A personal or project website.
  • Social handles (com.github, com.twitter).
  • Email (email).
06

Registrar & Registration Process

Names under the .eth TLD are acquired via a Vickrey auction system (for legacy names) or a straightforward registration process with an annual fee. The process involves:

  1. Requesting a name via the ENS Registrar controller.
  2. Committing a transaction to hide the request.
  3. Registering the name after a wait period, paying a fee based on name length (e.g., 5+ character names cost ~$5/year in ETH). Names are renewable and can be set to auto-renew.
ecosystem-usage
ENS (Ethereum Name Service)

Ecosystem Usage & Integrations

The Ethereum Name Service (ENS) is a distributed, open, and extensible naming system built on the Ethereum blockchain that maps human-readable names like alice.eth to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.

03

Profile & Identity Metadata

ENS supports rich metadata via text records, allowing names to store verifiable profile information on-chain. Common records include:

  • Email and URL for contact info.
  • Avatar (NFT or image URL) for visual identity.
  • Social handles (e.g., com.twitter, com.github).
  • Keywords and description for discoverability. This transforms .eth names into portable, user-controlled identity profiles used across DeFi, DAOs, and social platforms.
04

Cross-Chain Interoperability

Through CCIP Read, ENS enables resolution of names across multiple blockchains beyond Ethereum. This allows an ENS name to point to addresses on Layer 2s (like Arbitrum, Optimism) and other EVM-compatible chains (like Polygon, BNB Chain). The protocol uses off-chain gateways to fetch resolution data, making a single .eth name a universal identifier for a user's assets across the multi-chain ecosystem.

05

Subdomain Management & DAO Tools

ENS name owners can create unlimited subdomains (e.g., pay.company.eth) for free, which are useful for organizations, DAOs, and applications. DAO tooling platforms like Sybil use ENS for governance, allowing token-based voting power to be delegated to an ENS name for sybil resistance. Subdomains can be assigned different resolvers and records, enabling complex organizational structures.

06

Integration in DeFi & NFTs

ENS is deeply integrated into the DeFi and NFT ecosystem. Major protocols display ENS names in their UIs for improved UX. NFT marketplaces (OpenSea, Blur) show owner ENS names. Wallet explorers (Etherscan) resolve addresses to names. DApps use ENS for login systems (Sign-In with Ethereum) and to display user identities, creating a consistent naming layer across the entire Web3 stack.

examples
PRACTICAL APPLICATIONS

Common ENS Use Cases

The Ethereum Name Service (ENS) transforms blockchain addresses into human-readable names, enabling a wide range of practical applications beyond simple address resolution.

01

Human-Readable Wallet Addresses

The primary use case is replacing complex hexadecimal addresses (e.g., 0x71C7656EC7ab88b098defB751B7401B5f6d8976F) with simple names like alice.eth. This simplifies sending and receiving crypto payments, NFTs, and tokens, drastically reducing user error. It serves as a universal username across the Ethereum ecosystem and compatible blockchains.

02

Decentralized Website Hosting

ENS names can resolve to decentralized content hosted on the InterPlanetary File System (IPFS), Arweave, or Skynet. By setting a Content Hash record, yourname.eth can point to a personal website, portfolio, or dApp front-end that is censorship-resistant and available as long as the underlying network exists. This creates a truly decentralized web identity.

04

Subdomain Management for Organizations

Organizations can issue ENS subdomains (e.g., pay.company.eth) to departments, employees, or customers. This allows for:

  • Branded payment addresses for different business units.
  • Access control for team members.
  • Scalable identity systems without each user registering a primary .eth name. The root name owner maintains control over the entire subdomain namespace.
06

Cross-Chain Address Resolution

Through multicoin support, a single ENS name (e.g., bob.eth) can resolve to different addresses on various blockchains. This means bob.eth can point to an address on Bitcoin, Polygon, Solana, and Avalanche simultaneously. It creates a unified, chain-agnostic identity, simplifying multi-chain interactions where users no longer need to share a different address for each network.

ARCHITECTURE COMPARISON

ENS vs. Traditional DNS

A technical comparison of the Ethereum Name Service and the traditional Domain Name System across core architectural and operational dimensions.

Feature / DimensionEthereum Name Service (ENS)Traditional Domain Name System (DNS)

Underlying Infrastructure

Ethereum blockchain (decentralized ledger)

Hierarchical network of centralized servers

Control & Ownership

User-owned NFT; self-custodied via private key

Leased from a registrar; managed via account credentials

Censorship Resistance

Native Integration

Ethereum, EVM chains, IPFS, decentralized websites

Web2 internet (HTTP/HTTPS, email, traditional web)

Registration & Renewal Cost

One-time setup + annual gas fee (~$5-50/year)

Annual fee paid to registrar (~$10-15/year for .com)

Resolution Speed

~1-3 seconds (blockchain query latency)

< 100 milliseconds (optimized server lookup)

Primary Record Type

Cryptographic addresses (ETH, BTC, etc.)

IP addresses (A, AAAA records)

Decentralized Website Hosting

Native support (IPFS, Swarm, Arweave)

Requires centralized web server or CDN

technical-details
TECHNICAL ARCHITECTURE

ENS (Ethereum Name Service)

An overview of the decentralized naming system that maps human-readable names to machine-readable identifiers on the Ethereum blockchain and beyond.

The Ethereum Name Service (ENS) is a distributed, open, and extensible naming system built on the Ethereum blockchain that translates human-readable names like alice.eth into machine-readable identifiers such as Ethereum addresses, other cryptocurrency addresses, content hashes, and metadata. At its core, ENS functions similarly to the internet's Domain Name System (DNS), but it is decentralized, governed by a community of token holders, and secured by smart contracts on Ethereum. The primary components of its architecture are the ENS Registry—a central smart contract that maintains a record of all domains and subdomains—and Resolvers, which are separate contracts that hold the actual records (like addresses) for a given name.

The system operates through a hierarchical structure where the owner of a domain (e.g., example.eth) has full control over setting up subdomains (like wallet.example.eth) and configuring which resolver contract holds its records. This is managed via a process of registration and renewal, which for .eth names involves an annual fee paid in ETH, secured through a Vickrey auction-inspired mechanism called a permanent registrar. The architecture is designed to be interoperable, allowing ENS names to resolve not just to Ethereum resources but also to addresses on other blockchains (via cross-chain resolvers), IPFS content hashes, and even traditional website URLs through standardized interfaces.

From a technical perspective, interacting with ENS requires querying the registry contract to find the designated resolver for a name, then querying that resolver for the specific record type needed. This two-step resolution process provides flexibility, as different resolvers can be upgraded or specialize in different record types without affecting the core registry. ENS also supports DNS namespace integration, allowing owners of traditional DNS domains (like example.com) to import and manage them within the ENS system, thereby bridging Web2 and Web3 naming. Security is enforced by the underlying Ethereum blockchain, with ownership and record updates requiring cryptographic signatures from the name's controller.

The utility of ENS extends far beyond simplifying wallet addresses. It serves as a foundational decentralized identity primitive, enabling readable names for decentralized websites (hosted on IPFS or Arweave), user profiles with attached social metadata, and as a universal username across various dApps. Developers integrate ENS into their applications using libraries like ethers.js or web3.js, which provide methods for forward resolution (name to address) and reverse resolution (address to its primary ENS name). This architecture makes ENS a critical piece of infrastructure for human-readable interactions within the broader Web3 ecosystem.

security-considerations
ENS

Security Considerations

While ENS simplifies user experience, its interaction with the underlying blockchain introduces specific security risks that users and developers must understand.

01

Registrant vs. Controller

ENS names have two critical roles: the Registrant (owner of the name) and the Controller (entity that can update records). The Registrant holds the ultimate authority, represented by an NFT, and can transfer ownership or change the Controller. The Controller, often a wallet or smart contract, manages day-to-day operations like setting addresses. A common risk is losing access to the Registrant's private key, which results in permanent loss of the name. Best practice is to store the Registrant NFT in a hardware wallet.

02

Expiration & Name Squatting

ENS names are leased, not owned forever. They must be renewed before their expiration date to avoid lapsing. Once expired, the name enters a grace period and can be registered by anyone, leading to name squatting or theft. Attackers monitor for valuable names to expire. Mitigations include:

  • Setting long registration periods (e.g., multiple years).
  • Using automated renewal services or setting calendar reminders.
  • Understanding that a lapsed name can have its records (like linked addresses) immediately hijacked by a new owner.
03

Phishing & Homograph Attacks

ENS is vulnerable to visual deception attacks. Homograph attacks use Unicode characters from different alphabets that look identical to Latin letters (e.g., Cyrillic 'а' vs. Latin 'a') to create fake names like 'ethеreum.eth'. Phishing scams use these lookalike names to trick users into sending funds to the wrong address. Defenses include:

  • Users should always verify the full name and check for mixed scripts.
  • Wallets and dApps should implement Punycode decoding to reveal the true characters.
  • Being wary of names received via unsolicited messages.
04

Resolver & Record Integrity

The Resolver is a smart contract that stores and returns the records (like ETH addresses, IPFS hashes) for a name. Security risks include:

  • Using a malicious or compromised resolver contract that returns incorrect data.
  • The Controller setting records to point to malicious contracts or websites.
  • Front-running transactions when setting records on a public mempool. Users should verify the resolver address for trusted, audited contracts (like the public ENS resolver). Developers integrating ENS must validate returned data and not trust it blindly for high-value operations.
05

Wallet & Signature Risks

Interacting with ENS requires Ethereum transactions (register, set records, renew) signed by a private key. Key risks are:

  • Transaction Malleability: Signing a malicious transaction that transfers name ownership.
  • Approval Exploits: Granting excessive permissions to untrusted contracts that can later manipulate the name.
  • Social Engineering: Being tricked into signing a transaction that surrenders control. Users must meticulously verify every transaction's details before signing, especially when using ENS management dApps, and use hardware wallets for key management.
06

Subdomain Delegation Risks

Name owners can create subdomains (e.g., pay.merchant.eth) and delegate control to other addresses. This introduces delegation risks:

  • A compromised or malicious subdomain controller can set malicious records under the trusted parent domain.
  • Lack of clear visibility for end-users on who controls a specific subdomain.
  • Revocation complexity if a subdomain controller turns malicious. Parent domain owners must carefully audit and monitor entities they delegate to. Users should be aware that trust in a primary domain (.eth) does not automatically extend to all its subdomains.
evolution
EVOLUTION & GOVERNANCE

ENS (Ethereum Name Service)

The Ethereum Name Service (ENS) is a decentralized, open-source naming system built on the Ethereum blockchain that maps human-readable names like `alice.eth` to machine-readable identifiers such as Ethereum addresses, content hashes, and metadata.

The Ethereum Name Service (ENS) functions as a distributed, hierarchical domain name system for Web3, transforming complex cryptographic addresses into simple, memorable names. At its core, ENS operates through a system of registrars and resolvers. A registrar is a smart contract that manages the allocation of subdomain names (like .eth), while a resolver is a contract that translates a name into the associated resource, such as a wallet address or an IPFS hash. This architecture allows ENS to be extensible, supporting a wide array of record types beyond just cryptocurrency addresses.

Governance of the ENS protocol is managed by ENS DAO, a decentralized autonomous organization composed of $ENS token holders. The DAO oversees the protocol's treasury, funds ecosystem grants, and votes on key upgrades and parameter changes through a transparent, on-chain governance process. This model ensures that control of the naming standard is distributed among its users and developers, rather than a centralized entity, aligning with the core principles of decentralization and community ownership that underpin the Ethereum ecosystem.

The evolution of ENS has been marked by significant technical milestones, including the migration from an initial auction-based registrar for .eth names to the current permanent registrar, which uses a straightforward rent-based model with annual fees. The protocol has also expanded its namespace support beyond .eth to integrate with the traditional Domain Name System (DNS), allowing owners of DNS domains like example.com to claim the equivalent example.eth name. This cross-compatibility bridges Web2 and Web3, significantly broadening ENS's utility and user base.

ENS

Frequently Asked Questions (FAQ)

Essential questions and answers about the Ethereum Name Service (ENS), a decentralized naming system for blockchain addresses and data.

The Ethereum Name Service (ENS) is a decentralized, open-source naming system that maps human-readable names like alice.eth to machine-readable identifiers such as Ethereum addresses, IPFS content hashes, and other data. It works similarly to the internet's DNS but is built on the Ethereum blockchain. Users register a name by interacting with the ENS smart contracts, paying a small annual fee to a registrar to secure the name for a period. The system uses a hierarchical structure, where the owner of a domain (like .eth) has full control over subdomains, enabling decentralized management and censorship resistance.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
ENS (Ethereum Name Service) - Decentralized Naming System | ChainScore Glossary