Skip to content

Applications Dependent on ENS Subgraph (partial list)

Overview

The ENS Subgraph serves as a critical infrastructure component in the ENS ecosystem, providing indexed data that powers a wide range of applications and services. This page documents some examples of the extensive ecosystem that has been built around and depends on the ENS Subgraph, demonstrating why it will be critical that indexed ENS data remains available for ENSv2 through ENSNode.

ENS Subgraph Usage Metrics

The ENS Subgraph is a cornerstone of the current ENS architecture (ENSv1), handling an extraordinary volume of requests:

  • Approx 2 million avg daily requests
  • Over 717 million requests annually
ENS Subgraph usage metrics showing daily query volume
ENS Subgraph daily query volume following the transition to Graph Network hosting (June 20, 2024 onward)

This massive query volume underscores the central importance of the indexed ENS data and demonstrates the minimum scale at which any replacement solution must operate.

Ecosystem Impact

The ENS Subgraph’s influence extends across multiple categories of Web3 applications, from core infrastructure to end-user applications. Below is a partial list of projects and applications that depend on the ENS Subgraph for their functionality.

Critical ENS Apps & Infrastructure

  • Official ENS Manager App
    The primary interface for ENS domain management.

  • ENS Metadata Service
    Used by numerous services including:

    • NFT Marketplaces and APIs (OpenSea, etc.)
    • Rainbow Wallet
    • Rotki
  • ENSjs
    JavaScript library for ENS integration, used by many ENS-integrated applications

  • ENS Test Environment
    Testing framework for ENS development.

  • Linea Names
    Primary management interface for linea.eth subnames on Linea.

Chain Explorers

DAO Infrastructure

  • Snapshot.js
    TypeScript library for Snapshot integration.

DeFi Applications

  • Rotki
    Privacy preserving portfolio tracking.

Social Applications

ENS Marketplaces

Other Key Applications

Implications for ENSNode

The breadth of key applications dependent on indexed ENS data highlight the critical need for ENSNode. The growing ENS ecosystem requires a robust, scalable replacement of the ENS Subgraph that overcomes the ENS Subgraph’s limitations while simultaneously supporting ENSv2 and multichain ENS indexing (including Namechain).

Help Us Expand This List

Do you know of other applications that rely on the ENS Subgraph that aren’t listed here? Please contact us through the form on namehashlabs.org to let us know, and we’ll update this documentation.