ENSDb (SQL)

For special use cases that go beyond what the ENS Omnigraph exposes—you can query the live onchain state of both ENSv1 and ENSv2 directly via SQL.

ENSDb is a bi-directional integration standard for any EnsDbWriter and EnsDbReader implementations to coordinate around the live unified onchain state of ENSv1 and ENSv2 in a carefully-crafted standardized data model within a PostgreSQL database. Because ENSDb builds on Postgres, you can use any language with a Postgres driver—TypeScript, Python, Rust, Go, and more.

Coming soon: ensdb-cli & ENSDb snapshots

We’re building ensdb-cli & ENSDb snapshots so you can pull down a fresh ENSDb in minutes instead of paying for a full historical RPC backfill among many other benefits.

Self-hosting required

ENSDb is available when you self-host ENSNode. Each ENSNode instance writes its data into a PostgreSQL database that you own and control — that database is your ENSDb instance. The hosted ENSNode instances do not expose direct database access.

Inspirations for what you can build with ENSDb

Custom APIs

Build specialized GraphQL or REST APIs tailored to your use case. Query exactly the data you need with full SQL power.

Analytics & Dashboards

Create real-time dashboards and analytics pipelines. Better than Dune — you have the live ENS state locally with sub-second query latency.

CLIs & Developer Tools

Build command-line tools for ENS operations. Query domains, and any specialized lookup — all from your terminal.

Event-Based Engines

Build reactive systems that respond to ENS state changes. Respond to registration lifecycle updates, ownership transfers, resolver updates.

Data Pipelines

Feed ENS data into your existing data infrastructure. Sync to data warehouses, trigger webhooks, populate search indexes.

AI Agents

Build AI agents that can query ENS state and perform actions based on that data.

Example: fetch a Domain by canonical name

Canonical fields (canonical_name, canonical_path, canonical_node, canonical_depth) are populated on every Domain reachable from the canonical root, across both ENSv1 and ENSv2—query them uniformly without branching by type.

example.ts

import { EnsDbReader } from "@ensnode/ensdb-sdk";
import { eq } from "drizzle-orm";

const ensDbReader = new EnsDbReader(ensDbConnectionString, ensIndexerSchemaName);
const { ensDb, ensIndexerSchema } = ensDbReader;

const [vitalik] = await ensDb
  .select()
  .from(ensIndexerSchema.domain)
  .where(eq(ensIndexerSchema.domain.canonicalName, "vitalik.eth"));

example.sql

SELECT * FROM ensindexer_0.domains
WHERE canonical_name = 'vitalik.eth';

Example: count an address’s Domains by type (ENSv1 vs ENSv2)

example.ts

import { count, eq } from "drizzle-orm";

const counts = await ensDb
  .select({ type: ensIndexerSchema.domain.type, count: count() })
  .from(ensIndexerSchema.domain)
  .where(eq(ensIndexerSchema.domain.ownerId, "0xd8da6bf26964af9d7eed9e03e53415d37aa96045"))
  .groupBy(ensIndexerSchema.domain.type);

example.sql

SELECT type, count(*) FROM ensindexer_0.domains
WHERE owner_id = '0xd8da6bf26964af9d7eed9e03e53415d37aa96045'
GROUP BY type;

Learn more

ENSDb overview Architecture, schemas, what you can build, and quick-start guides.

ENSDb SDK (TypeScript) Type-safe database access and utilities for working with ENSDb.

ENSDb SQL interface Connect with any PostgreSQL client and run queries directly.

Self-host ENSNode Run your own ENSNode instance to get full ENSDb access.