datasources

@ensnode/datasources

This package provides contract configurations (chain, names, addresses, abis) for each known ENS Namespace. An ENS Namespace represents a single, unified set of ENS names with a distinct onchain ensroot Datasource and an optional set of additional Datasources on different chains (and, in the future, offchain datasources).

For example, the canonical ENS Namespace on mainnet includes:

• A ensroot Datasource documenting the ENS contracts on mainnet, including the .eth subregistry
• A basenames Datasource documenting the Basenames contracts on Base, including the .base.eth subregistry
• A lineanames Datasource documenting the Basenames contracts on Linea, including the .linea.eth subregistry
• The threedns-optimism and threedns-base Datasources documenting the 3DNS contracts on Optimism and Base, respectively
• 🚧 Various offchain Datasources (e.g. .cb.id, .uni.eth)

Each ENS namespace is logically independent and isolated from the others: for instance, the sepolia and holesky testnet namespaces manage a set of names that is entirely separate from the canonical mainnet namespace, and have distinct basenames and lineanames Datasources defined.

The ens-test-env namespace describes the contracts deployed to an Anvil chain for development and testing with the ens-test-env tool.

Usage

To use these configurations in your project:

import { getDatasource } from "@ensnode/datasources";
import { namehash } from "viem";

// access the address and abi for the ens root Registry in the canonical mainnet ENS namespace
const registryConfig = getDatasource('mainnet', 'ensroot').contracts.Registry;

// for example, querying the Registry with viem...
const vitaliksResolverAddress = await publicClient.readContract({
  abi: registryConfig.abi,
  address: registryConfig.address,
  functionName: "resolver",
  args: [namehash("vitalik.eth")],
});

See the usage of @ensnode/datasources within ENSIndexer for additional context.

Documentation

getDatasource(namespaceId: ENSNamespaceId, datasourceName: DatasourceName)

The primary export of @ensnode/datasources is getDatasource which returns a selected Datasource within the selected ENS namespace.

import { getDatasource } from '@ensnode/datasources';

// get ensroot datasource relative to mainnet ENS namespace
const { chain, contracts } = getDatasource('mainnet', 'ensroot');

// get ensroot datasource relative to holesky ENS namespace
const { chain, contracts } = getDatasource('holesky', 'ensroot');

// get threedns-base datasource relative to mainnet ENS namespace
const { chain, contracts } = getDatasource('mainnet', 'threedns-base');

The available ENSNamespaceIds are:

• mainnet
• sepolia
• holesky
• ens-test-env — Represents a local testing namespace running on an Anvil chain (chain id 1337) with deterministic configurations that deliberately start at block zero for rapid testing and development. See ens-test-env for additional context.

DatasourceName

Each ENS namespace my provide Datasource entries for any of the possible DatasourceNames:

The available DatasourceNames are:

• ensroot — ENS Root Contracts, guaranteed to exist
• basenames — Basenames, optional
• lineanames — Linea Names, optional
• threedns-optimism — 3DNS (on Optimism), optional
• threedns-base — 3DNS (on Base), optional

A Datasource will only be available within an ENS namespace if it is defined, and typescript will enforce that a valid DatasourceName is used within getDatasource(...).

Datasource

A Datasource describes a source chain and the set of contracts on that chain that integrate with the ENS protocol.

• chain — a viem#Chain object
• contracts — a Record<DatasourceName, ContractConfig>

ContractConfig

A ContractConfig defines the necessary information to interact with a specific contract within a Datasource, and is directly compatible with ponder#ContractConfig for ease of use within a Ponder indexer.

• abi — the contract's ABI
• address — (optional) the contract's deployed address
• filter — (optional) array of event signatures to filter logs by
• startBlock — the block number when the contract was deployed

A contract can be located either by its static address or by filtering for specific event signatures. Note that either address or filter must be provided, but not both.

If a filter is provided, the relevant contract is any contract on the indicated chain that emits events following the filter spec. This occurs, namely, for Resolver contracts — any contract that emits an event that looks like a Resolver event should be considered a Resolver for the purposes of indexing ENS data.

Contributions

We welcome community contributions and feedback—please see CONTRIBUTING.md for more information.

Contact Us

Visit our website to get in contact, or join us on Telegram.

License

Licensed under the MIT License, Copyright © 2025-present NameHash Labs.

See LICENSE for more information.