Buyers register new domains and renew existing ones for which they pay a fee (revenue).

Ethereum Name Service (ENS) is an extensible naming system built on Ethereum with similar goals to the Domain Name System (DNS). ENS was founded by Nick Johnson and launched in 2017.

ENS token holders own and govern the protocol. They currently take the full share of all registration and renewal fees.

governance

github

twitter

discord

etherscan

website

Infrastructure

Ethereum Name Service

# Ethereum Name Service Active users (daily) Methodology

## 1. Overview

ENS (Ethereum Name Service) daily active users measures the number of unique wallet addresses that perform ENS-related activities on a given day. This metric captures user engagement with ENS infrastructure by tracking two primary activities: domain registrations (new .eth domain purchases) and domain renewals (extending existing domain expiration dates). The calculation aggregates distinct user addresses per day across all ENS contract interactions on Ethereum.

## 2. Data sources

- **ENS contract function calls**: Parsed Ethereum function call data from ENS controller contracts including `ETHRegistrarControllerV2`, `ETHRegistrarController`, and `BaseRegistrarImplementation` for domain renewal activities
- **ENS contract events**: Parsed Ethereum event logs from ENS registrar controller contracts capturing `NameRegistered` events for new domain registrations
- **Ethereum transaction data**: Transaction metadata including block timestamps, transaction hashes, and execution status for filtering successful interactions

## 3. Step-by-step calculation

### Component A: ENS renewal user activity
- **Purpose**: Captures users who renew existing ENS domains
- **Logic**: Extracts function call data from three ENS controller contracts where users call renewal functions. Identifies the transaction sender (`from_address`) as the renewing user. Filters for successful transactions where `status` equals true. Classifies these users as "Renewer" type and assigns them to the infrastructure market sector and identity business segment.
- **Key fields**: `block_timestamp` for timing, `from_address` as the user identifier, `transaction_hash` for deduplication, and transaction `status` for filtering

### Component B: ENS registration user activity  
- **Purpose**: Captures users who register new ENS domains
- **Logic**: Extracts event log data from `NameRegistered` events emitted by ENS registrar controller contracts when new domains are purchased. Identifies the domain owner (`owner` parameter) as the registering user. Filters for valid events where `removed` equals false. Classifies these users as "Registerer" type and assigns them to the infrastructure market sector and identity business segment.
- **Key fields**: `block_timestamp` for timing, `owner` parameter as the user identifier, `transaction_hash` for deduplication, and `removed` flag for filtering

### Final aggregation
- **Combining components**: Union all renewal function calls and registration events into a single user activity dataset, standardizing the user address field and maintaining user type classification
- **Time aggregation**: Truncate all block timestamps to daily boundaries using day-level granularity, grouping all activities within the same calendar day
- **Daily active user calculation**: Count distinct user addresses per day across all ENS activities, regardless of user type or number of transactions performed by each address
- **Final output**: Generate daily counts of unique wallet addresses that interacted with ENS contracts, providing a measure of daily user engagement with ENS infrastructure

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique revenue-generating users over a fixed 24-hour window.

Ethereum Name ServiceENS

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown