ENS Subgraph

The ENS Subgraph is legacy — do not build new ENS apps on it!

The ENS Subgraph predates ENSv2 and cannot carry your app into it. Three reasons it falls short:

• ENSv1 only — instantly out of date. The Subgraph data model has no concept of ENSv2. The moment ENSv2 launches (Summer 2026), apps still reading the Subgraph are looking at a stale, partial view of ENS.
• Single-chain only — misses most names. The Subgraph indexes a single chain, so it never sees Basenames (.base.eth), Lineanames (.linea.eth), or 3DNS names (.box).
• No resolution — and slow when you bolt it on. The Subgraph doesn’t resolve names; you’re left making your own RPC calls, which are slow, hard to batch, and easy to get wrong.

These are only the headline issues. See the full list of Key Limitations.

Start here instead: the ENS Omnigraph API

The ENS Omnigraph API is the ENSv2-ready replacement: one unified, typed GraphQL API over both ENSv1 and ENSv2, multichain by default, with protocol-correct ENS Protocol Acceleration resolution built in.

ENS Omnigraph API ENSv2-ready unified GraphQL API over both ENSv1 and ENSv2 — start here for new integrations.

ENS Unigraph SQL Direct SQL access to the unified, multichain ENS data model.

The ENS Subgraph became critical infrastructure

Over the years, the ENS Subgraph quietly became one of the most depended-on pieces of infrastructure in ENS. An enormous swath of the ENS ecosystem — and much of the broader web3 / Ethereum ecosystem — reads ENS data through it, directly or indirectly.

Usage at scale

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

• Approx. 2 million average daily requests
• Over 717 million requests annually

ENS Subgraph daily query volume following the transition to Graph Network hosting (June 20, 2024 onward)

This volume sets the floor: it’s the minimum scale at which any replacement must operate.

Applications dependent on the ENS Subgraph

The list below is a partial map of the projects and applications that depend on the ENS Subgraph for their functionality — directly, or indirectly through services like the ENS Metadata Service, ENSjs, or the Ethereum Comments Protocol. When ENSv2 launches, indexed ENS data must keep flowing to all of these, or they break.

Critical ENS Apps & Infrastructure

• Official ENS Manager App — the primary interface for ENS domain management.
• ENS Metadata Service — used by numerous downstream services including NFT marketplaces (OpenSea, Rarible), Rainbow Wallet, and 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.

ENS Registrars

• Grails — by the EthId Foundation.
• ENS Vision
• OpenSea and Rarible — via their dependency on the ENS Metadata Service.
• ENS Tools
• Snipe Zone
• Nameful — by Blockful.

Wallets

• Rainbow Wallet — mobile wallet and browser extension.
• MyEtherWallet — Ethereum wallet.
• Safe Transaction Service — by Safe.

Chain Explorers

• Blockscout — blockchain explorer platform.
• EthVM — by MyEtherWallet.
• Cartesi Explorer — by Cartesi.

DAO Infrastructure

• Snapshot.js — TypeScript library for Snapshot integration.
• Snapshot — via Stamp. This is a distinct integration from snapshot.js.
• DAOStar — by Metagov.
• ENS Metadata Manager — by Lighthouse (more info).
• Optimism GovQuests — by Bleu.

ENS History Viewers

• ENSvolution — by JustaName.
• PastENS
• Swiss Knife — by apoorv.eth.
• ENS Wayback Machine — by Blossom.

ENS Developer Tools

• ENS Resolver — by Andrew Raffensperger.
• ENS Tools — by ENS Labs.
• ENS Tools — by Serenae.

ENS CLI Tools

• Atlas — by Steve Dylan.
• Ensemble — by estmcmxci.
• Basenames CLI — by estmcmxci.
• Grails CLI — by the EthId Foundation (uses the Grails API, which uses ENSNode).

ENS MCP Servers

• ENS MCP Service — by Namespace.
• ENS MCP Service — by JustaName.
• ENS MCP Service — by Kukapay.

ENS Avatar & Metadata Services

• Stamp — by Snapshot Labs.
• ENS Metadata Flarecloud — by the EthId Foundation.

ENS Contract Naming Platforms

• Enscribe

Ethereum Libraries

• safe-eth-py — by Safe.

ENS Social Media Services

• ENS Market Bot — by the EthId Foundation.

AI Agents / x402 / Micropayments / Proof of Humanity

• Skills — by Namespace.
• PrismOS
• HumanENS (GitHub)
• nayym (GitHub)

DeFi Applications

• Rotki — privacy-preserving portfolio tracking.

Social Applications

• Ethereum Follow Protocol — onchain social graph protocol.
• LinkChain (GitHub)
• Dapp Rank — by Joel Thorstensson.
• Decentraland Builder (GitHub) — by Decentraland.
• Decentraland Creator Hub (GitHub) — by Decentraland.

Other Key Applications

• ENSPro — by NameStone.
• ENSBook — by Liuliuben.
• L2 Subnames — by Namespace.
• ENS Data — by Pugson.
• ENS Ideas — by Frolic.
• Next.ID — which also powers Web3.bio (by Yan Zhu) and Eth.cd (by Webhash / Hid).

Help us expand this list

Do you know of other applications that rely on the ENS Subgraph that aren’t listed here? Please open a PR to update this documentation.

What this means

The breadth of applications above shows that indexed ENS data is critical infrastructure for ENS and the broader ecosystem — and that there is large, proven demand for it today. When ENSv2 launches, the Subgraph’s Key Limitations become breaking for these apps. ENSNode exists to keep indexed ENS data flowing through the transition and beyond, with a robust, scalable, multichain, ENSv2-ready replacement.

Already building directly on ENSNode

A growing set of companies and apps have already moved onto ENSNode and future-proofed their ENS applications — see who’s already building on ENSNode.

Next Steps

Next, consider the key limitations of the legacy ENS Subgraph.

Key Limitations The full list of ways the ENS Subgraph falls short — and gets worse with ENSv2.

Or, prepare your app or platform for ENSv2 by adopting ENSNode’s Omnigraph API.

ENS Omnigraph API The ENSv2-ready replacement. Start here for new integrations.