Keep ENS apps working 🚨
The ENS Subgraph is not ENSv2 compatible
Section titled “The ENS Subgraph is not ENSv2 compatible”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
Section titled “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
Section titled “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.
ENS Registrars
Section titled “ENS Registrars”Upgrade to Omnigraph required
Official ENS Manager App — the official interface for ENS domain registration and management.
Grails — by the EthId Foundation.
Linea Names — primary management interface for linea.eth subnames on Linea.
Wallets
Section titled “Wallets”Upgrade to Omnigraph required
Safe Transaction Service — by Safe.
Rotki — privacy-preserving portfolio tracking.
Chain Explorers
Section titled “Chain Explorers”Upgrade to Omnigraph required
EthVM — by MyEtherWallet.
Cartesi Explorer — by Cartesi.
DAO Infrastructure
Section titled “DAO Infrastructure”Upgrade to Omnigraph required
Snapshot.js — TypeScript library for Snapshot integration.
ENS Metadata Manager — by Lighthouse (more info).
Optimism GovQuests — by Bleu.
ENS History Viewers
Section titled “ENS History Viewers”Upgrade to Omnigraph required
ENSvolution — by JustaName.
Swiss Knife — by apoorv.eth.
ENS Wayback Machine — by Blossom.
Developer Tools
Section titled “Developer Tools”Upgrade to Omnigraph required
Enscribe — ENS contract naming platform
ENSjs — The official ENS JavaScript library.
ENS Test Environment — The official testing environment for ENS development.
ENS Resolver — by Andrew Raffensperger.
ENS Tools — by Serenae.
safe-eth-py — by Safe.
ENS CLI Tools
Section titled “ENS CLI Tools”Upgrade to Omnigraph required
Atlas — by Steve Dylan.
Basenames CLI — by estmcmxci.
Grails CLI — by the EthId Foundation (uses the Grails API, which uses ENSNode).
ENS AI Agents
Section titled “ENS AI Agents”Upgrade to Omnigraph required
ENS MCP Service — by Namespace.
ENS MCP Service — by JustaName.
ENS MCP Service — by Kukapay.
ENS Avatar & Metadata Services
Section titled “ENS Avatar & Metadata Services”Upgrade to Omnigraph required
ENS Metadata Service — the primary service used across the ENS ecosystem for loading ENS avatar images.
Stamp — by Snapshot Labs.
ENS Metadata Flarecloud — by the EthId Foundation.
Social Applications
Section titled “Social Applications”Upgrade to Omnigraph required
Ethereum Follow Protocol — onchain social graph protocol.
Dapp Rank — by Joel Thorstensson.
Decentraland Builder (GitHub) — by Decentraland.
Decentraland Creator Hub (GitHub) — by Decentraland.
ENS Market Bot — by the EthId Foundation.
Subname Providers
Section titled “Subname Providers”Upgrade to Omnigraph required
L2 Subnames — by Namespace.
What this means
Section titled “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
Section titled “Already building directly on ENSNode”A growing set of companies and apps have already moved onto ENSNode — see who’s already building on ENSNode.
Next Steps
Section titled “Next Steps”Next, consider the key limitations of the legacy ENS Subgraph.
Or, prepare your app or platform for ENSv2 by adopting ENSNode’s Omnigraph API.