Why ENSNode?
This page will explain why ENSNode is the best way to build ENSv2 applications — including ENSNode’s ENSv2 readiness, multichain support, how it compares to the legacy ENS Subgraph, and much more.
Why it’s important for ENS?
Section titled “Why it’s important for ENS?”ENSv2 introduces a completely new onchain data model we refer to as the ENS Namegraph. Additionally, when ENSv2 launches, ENSv1 continues to exist in parallel. The legacy ENS Subgraph cannot support ENSv2. Apps building on ENSv2 need a simple and powerful solution for querying the full unified state of ENSv1 and ENSv2. ENSNode delivers this as a full-stack of integration points for developers building on the future of ENS. Learn more
Close critical ENS infrastructure gaps
Section titled “Close critical ENS infrastructure gaps”Indexed ENS data is vital for the upcoming launch of ENSv2. Existing ENS indexed data providers (the ENS Subgraph) are fundamentally unsuitable for ENSv2 and a replacement is critically required for many of ENS’s most important apps, including the official ENS Manager App among many others.
Strengthen the decentralization and “unstoppability” of ENS
Section titled “Strengthen the decentralization and “unstoppability” of ENS”Our infrastructure under development removes a strict dependency on many centralized offchain gateway servers whose downtime would otherwise shut down impacted multichain ENS names that are key to the future of ENSv2, such as subnames of base.eth, linea.eth, or tokenized DNS names such as .box names or 3DNS names.