Why ENSNode?
ENSNode is the full-stack ENSv2 development platform — a single, unified API over both ENSv1 and ENSv2, with first-class multichain support and the integration surfaces (React, TypeScript, GraphQL, Postgres) you need to ship.
Built for ENSv2 from day one
Section titled “Built for ENSv2 from day one”ENSv2 is a fundamental change to ENS’s onchain data model. The legacy ENS Subgraph wasn’t designed for it, and it never will be — single-chain, no resolution, no understanding of the new Namegraph. Apps that stay on the Subgraph will be left behind the moment ENSv2 launches.
ENSNode is built around ENSv2 from the ground up. The same query works against an ENSv1 name today and an ENSv2 name the moment it goes live — with zero downtime or code changes in your app.
One unified API over ENSv1 + ENSv2
Section titled “One unified API over ENSv1 + ENSv2”The ENS Omnigraph is a single GraphQL API that returns a polymorphic, unified view of every ENS Domain — regardless of whether it lives in the ENSv1 nametree, the ENSv2 Namegraph, on mainnet, or on an L2 subregistry.
ENSv1 and ENSv2 coexist after the ENSv2 launch. The Omnigraph hides that split: your code asks for domain(by: { name: "vitalik.eth" }) and gets a typed result, regardless of whether the underlying domain is on ENSv1 or ENSv2.
Multichain by default
Section titled “Multichain by default”ENSNode indexes the full ENS namespace across every chain that matters, all from one query:
- Mainnet — the canonical ENS root and
.ethregistrations - Basenames (
.base.eth) on Base - Lineanames (
.linea.eth) on Linea - 3DNS names (
.box, tokenized DNS) on Optimism and Base
No more wiring up a per-chain Subgraph, reconciling overlapping namespaces, or writing CCIP-Read logic in your app — ENSNode handles forward and reverse resolution, including offchain gateways, server-side.
Full-stack integration surfaces
Section titled “Full-stack integration surfaces”Whatever your stack looks like, there’s an ENSNode integration shaped for it:
Why it matters beyond your app
Section titled “Why it matters beyond your app”Close critical ENS infrastructure gaps
Section titled “Close critical ENS infrastructure gaps”Indexed ENS data is vital for the upcoming launch of ENSv2. The legacy ENS Subgraph is fundamentally unsuitable for ENSv2, and a replacement is critically required for many of ENS’s most important apps — including the official ENS Manager App.
Strengthen the decentralization and “unstoppability” of ENS
Section titled “Strengthen the decentralization and “unstoppability” of ENS”ENSNode removes the strict dependency on centralized offchain gateway servers whose downtime would otherwise shut down impacted multichain ENS names that are key to the future of ENSv2 — subnames of base.eth, linea.eth, tokenized DNS names like .box, and more.