https://github.com/namehash/ensnode
The new multichain indexer for ENSv2, powered by Ponder.
https://github.com/namehash/ensnode
ens indexer ponder subgraph
Last synced: about 1 month ago
JSON representation
The new multichain indexer for ENSv2, powered by Ponder.
- Host: GitHub
- URL: https://github.com/namehash/ensnode
- Owner: namehash
- License: mit
- Created: 2024-12-23T17:34:54.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-04-21T22:31:58.000Z (about 2 months ago)
- Last Synced: 2026-04-22T00:28:41.200Z (about 2 months ago)
- Topics: ens, indexer, ponder, subgraph
- Language: TypeScript
- Homepage: https://ensnode.io
- Size: 36.2 MB
- Stars: 39
- Watchers: 1
- Forks: 16
- Open Issues: 290
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
- Agents: AGENTS.md
Awesome Lists containing this project
README
# ENSNode
ENSNode is the new multichain indexer for ENS, including [ENSv2](https://roadmap.ens.domains/roadmap/).
Full Documentation ➡︎ ensnode.io
[Join us on Telegram](https://t.me/ensnode) to get support, share ideas, and discuss the future of ENSNode.
## The future of ENS indexing
ENSNode provides enhanced ENS indexing capabilities beyond the ENS Subgraph, including faster indexing and simpler self-hosted deployments. Initial multichain capabilities include indexing mainnet, Basenames, Lineanames, 3DNS, and more, providing a unified multichain namespace via a subgraph-compatible GraphQL API. When exclusively activating our subgraph plugin, ENSNode has full data equivalency with the ENS Subgraph.
- Multichain ENS Namespace
- flattened, unified, multichain and multiregistrar namespace via optional plugins
- ✅ All names added to the ENS Registry and the ENS NameWrapper
- ✅ All direct subnames of .eth
- ✅ [Basenames](https://www.base.org/names) (`.base.eth`)
- ✅ [Lineanames](https://names.linea.build/) (`.linea.eth`)
- ✅ [3DNS](https://3dns.box) Support (`.box`, `.xyz`, +more)
- 🚧 Offchain Names
- `.cb.id`, `.uni.id`, + more
- [NameStone](https://namestone.com/) Names
- [NameSpace](https://namespace.ninja/) Names
- [Justaname](https://www.justaname.id/) Names
- 🚧 + more
- Built on [Ponder](https://ponder.sh)
- ✅ Rapid Indexing & Backfill
- 10x faster than ENS Subgraph
- Mainnet Cached Backfill: **4.5 hours** on M1 Macbook Pro
- ✅ More efficient than ENS Subgraph
- 35x less disk space and 35% fewer RPC credits [[source]](https://ponder.sh/docs/why-ponder)
- ✅ End-to-end type safety
- ✅ Automatically reconciles chain reorganizations
- ✅ Deploy anywhere with Node.js & Docker
- Designed for web developers
- ✅ [use ENSNode with ENSjs](https://ensnode.io/docs/usage/with-ensjs)
- ✅ [GraphQL APIs](https://ensnode.io/docs/usage/api)
- ✅ Custom APIs for your app
- [1:1 Subgraph Compatibility](https://ensnode.io/docs/concepts/what-is-the-ens-subgraph)
- ✅ [100% data equivalency](https://github.com/namehash/ens-subgraph-transition-tools) as compared to Subgraph
- ✅ 100% ensjs test suites passing via [ens-test-env](https://github.com/namehash/ens-test-env)
- ✅ 100% ens-app-v3 test suites passing via [ens-test-env](https://github.com/namehash/ens-test-env)
- Own your ENSNode index
- ✅ [Deploy ENSNode to your own cloud](https://ensnode.io/docs/deploying) for controlling your own uptime guarantees and private queries
## Why Index ENS? Why ENSNode?
The ENS protocol enables resolution of names across multiple chains and, increasingly, offchain data sources. ENS smart contracts optimize for some operations, but not others: for example, if you wanted to list all of a user's owned names, there's no practical way to do this through ENS contracts, and an indexer like ENSNode _must_ be used.
An indexer aggregates and reorganizes the representation of ENS's state to make important queries like that possible, efficient, and convenient:
```graphql
# get all of a user's domains by address — not possible on-chain!
query Domains($adress: String!) {
domains(where: { owner: $address }) {
id
name
...
}
}
```
Historically the ENS Subgraph has served this purpose, but the Subgraph's limitations are increasingly severe as the ENS protocol grows: the ENS Subgraph can only index a single chain at a time (ex: mainnet) and can't integrate with names or that require [CCIP-Read](https://docs.ens.domains/resolvers/ccip-read), which includes all names stored on L2 chains or offchain.
Given how the majority of ENS names are now issued off of mainnet, only a small percentage of ENS names can be indexed by the ENS Subgraph. This issue will only grow more severe with the launch of [ENSv2](https://roadmap.ens.domains/roadmap/) and [Namechain](https://app.ens.domains/ens-v2).
ENSNode is a modern, multichain indexer for ENS. It supports backwards-compatible Subgraph queries and sets the stage for supporting [ENSv2](https://roadmap.ens.domains/roadmap/), in particular [Namechain](https://app.ens.domains/ens-v2) and the growing set of off-chain ENS names (like `.uni.eth` and `.cb.id`).
## Documentation
Documentation for the ENSNode suite of apps is available at [ensnode.io](https://ensnode.io).
## Running with Docker
```bash
docker compose -f docker/docker-compose.yml up -d
```
See [`docker/README.md`](docker/README.md) for all use cases and commands.
## Contributions
We welcome community contributions and feedback—please see [CONTRIBUTING.md](CONTRIBUTING.md) for more information.
## Sponsors
NameHash has received generous support from the [ENS DAO](https://ensdao.org/) and [Gitcoin](https://www.gitcoin.co/).
## Contact Us
Visit our [website](https://namehashlabs.org/) to get in contact, or [join us on Telegram](https://t.me/ensnode).
## License
Licensed under the MIT License, Copyright © 2025-present [NameHash Labs](https://namehashlabs.org).
See [LICENSE](./LICENSE) for more information.
## Repo Overview
The ENSNode monorepo contains multiple modules in the following subdirectories:
- [`apps`](apps) executable applications.
- [`packages`](packages) for libraries that can be embedded into apps.
- [`docs`](docs) documentation sites.
### [`apps/ensadmin`](apps/ensadmin)
ENSAdmin is a dashboard for ENSNode and the ENS protocol. See the [ENSAdmin documentation](https://ensnode.io/ensadmin) for more details.
### [`apps/ensindexer`](apps/ensindexer)
ENSIndexer is a Ponder-powered indexer for ENS across multiple chains. See the [ENSIndexer documentation](https://ensnode.io/ensindexer) for more details.
### [`apps/ensrainbow`](apps/ensrainbow)
ENSRainbow heals unknown ENS names: it provides a simple API to recover labels from their labelHashes. See the [ENSRainbow documentation](https://ensnode.io/ensrainbow) for more details.
## Packages
### [`packages/ensdb-sdk`](packages/ensdb-sdk)
Software Development Kit for interacting with data in ENSDb.
### [`packages/ensnode-sdk`](packages/ensnode-sdk)
Software Development Kit for interacting with ENSNode services and data. Includes common utilities used across ENSNode applications.
### [`packages/ensnode-react`](packages/ensnode-react)
React hooks and providers for the ENSNode API.
### [`packages/datasources`](packages/datasources)
Convenient catalog of ENSNode-related datasources including chain, contract addresses, start blocks, and event filters.
### [`packages/ensrainbow-sdk`](packages/ensrainbow-sdk)
TypeScript library for interacting with the [ENSRainbow API](apps/ensrainbow).
### [`packages/ponder-sdk`](packages/ponder-sdk)
A utility library for interacting with Ponder apps and data.
### [`packages/ponder-subgraph`](packages/ponder-subgraph)
Subgraph-compatible GraphQL API.
### [`packages/shared-configs`](packages/shared-configs)
Shared internal configuration files.
## Docs
### [`docs/ensnode.io`](docs/ensnode.io/)
Astro/Starlight documentation app for ENSNode, ENSIndexer, ENSAdmin, and ENSRainbow.
### [`docs/ensrainbow.io`](docs/ensrainbow.io/)
Landing page for ENSRainbow.
