Skip to content

Keep ENS apps working 🚨

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.

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 usage metrics showing daily query volume

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. When ENSv2 launches, indexed ENS data must keep flowing to all of these, or they break.

Upgrade to the ENS Omnigraph required

Official ENS Manager App — the official interface for ENS domain registration and management.

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.

Linea Names — primary management interface for linea.eth subnames on Linea.

ENSBook — by Liuliuben.

ENS Ideas — by Frolic.

Upgrade to the ENS Omnigraph required

Rainbow Wallet
MyEtherWallet

Safe Transaction Service — by Safe.

Rotki — privacy-preserving portfolio tracking.

Upgrade to the ENS Omnigraph required

Blockscout

EthVM — by MyEtherWallet.

Cartesi Explorer — by Cartesi.

Upgrade to the ENS Omnigraph required

Snapshot — via Stamp. This is a distinct integration from snapshot.js.

Snapshot.js — TypeScript library for Snapshot integration.

DAOStar — by Metagov.

ENS Metadata Manager — by Lighthouse (more info).

Optimism GovQuests — by Bleu.

Upgrade to the ENS Omnigraph required

ENSvolution — by JustaName.

PastENS

Swiss Knife — by apoorv.eth.

ENS Wayback Machine — by Blossom.

Upgrade to the ENS 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 ENS Labs.

ENS Tools — by Serenae.

ENS Data — by Pugson.

safe-eth-py — by Safe.

Upgrade to the ENS Omnigraph required

Atlas — by Steve Dylan.

Ensemble — by estmcmxci.

Basenames CLI — by estmcmxci.

Grails CLI — by the EthId Foundation (uses the Grails API, which uses ENSNode).

Upgrade to the ENS Omnigraph required

ENS MCP Service — by Namespace.

ENS MCP Service — by JustaName.

ENS MCP Service — by Kukapay.

Skills — by Namespace.

PrismOS

HumanENS (GitHub)

nayym (GitHub)

Upgrade to the ENS 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.

Upgrade to the ENS Omnigraph required

Ethereum Follow Protocol — onchain social graph protocol.

Next.ID

Web3.bio — builds on Next.ID.

Eth.cd — builds on Next.ID, by Webhash.

ENS Market Bot — by the EthId Foundation.

LinkChain (GitHub)

Dapp Rank — by Joel Thorstensson.

Decentraland Builder (GitHub) — by Decentraland.

Decentraland Creator Hub (GitHub) — by Decentraland.

Upgrade to the ENS Omnigraph required

L2 Subnames — by Namespace.

ENSPro — by NameStone.

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.

A growing set of companies and apps have already moved onto ENSNode — see who’s already building on ENSNode.

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

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