Unigraph SQL Examples

These examples show the same queries two ways: in raw SQL (any PostgreSQL client, any language) and with the typed @ensnode/ensdb-sdk for TypeScript projects.

SQL access requires connecting to your own self-hosted ENSDb instance.

Connect

The Unigraph lives in ENSDb, a PostgreSQL database. Each ENSIndexer instance writes to its own ENSIndexer Schema (e.g. ensindexer_0); shared operational metadata lives in the ensnode schema.

SQL

# Production environment (mainnet data)
psql postgresql://user:password@host:5432/ensdb_mainnet

# Pre-production environment (testnet data)
psql postgresql://user:password@host:5432/ensdb_testnet

# Staging / local development environment
psql postgresql://user:password@host:5432/ensdb_devnet

Discover the available ENSIndexer Schemas:

SELECT DISTINCT ens_indexer_schema_name
FROM ensnode.metadata;

ensdb-sdk (TypeScript)

npm install @ensnode/ensdb-sdk

import { EnsDbReader } from '@ensnode/ensdb-sdk';

// Connect by providing a connection string and the ENSIndexer Schema Name to query
const ensDbReader = new EnsDbReader(ensDbConnectionString, ensIndexerSchemaName);
const { ensDb, ensIndexerSchema } = ensDbReader;

Canonical fields

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.

Examples

Domain by Name

Account Domains

Indexing Status