Integrate ENSDb SDK into ENSIndexer

.changeset/beige-brooms-prove.md

@@ -0,0 +1,5 @@
+---
+"ensindexer": minor
+---
+
+Replaced a bespoke `EnsDbClient` implementation with `EnsDbWriter` from ENSDb SDK.

.changeset/common-mangos-sort.md

@@ -0,0 +1,5 @@
+---
+"ensindexer": minor
+---
+
+Added running database migrations for ENSDb as a responsibility for ENSIndexer.

.changeset/quick-years-divide.md

@@ -0,0 +1,6 @@
+---
+"@ensnode/ensnode-sdk": minor
+"@ensnode/ensdb-sdk": minor
+---
+
+Moved `ensdb` module from ENSNode SDK into ENSDb SDK.

.changeset/thin-humans-punch.md

@@ -0,0 +1,5 @@
+---
+"@ensnode/ensdb-sdk": minor
+---
+
+Introduced two client implementations for ENSDb: `EnsDbReader` and `EnsDbWriter`.

apps/ensindexer/ponder/ponder.schema.ts

@@ -1,2 +1,6 @@
-// export database schema definition for ENSIndexer
-export * from "@ensnode/ensdb-sdk/ensindexer";
+/**
+ * We re-export (just) the "abstract" ENSIndexer Schema from ENSDb for Ponder to manage.
+ * Ponder will internally build a "concrete" ENSIndexer Schema using
+ * the "abstract" ENSIndexer Schema and the ENSIndexer Schema name.
+ **/
+export * from "@ensnode/ensdb-sdk/ensindexer-abstract";

apps/ensindexer/ponder/src/api/handlers/ensnode-api.ts

@@ -10,13 +10,13 @@ import {
   serializeIndexingStatusResponse,
 } from "@ensnode/ensnode-sdk";
 
-import { ensDbClient } from "@/lib/ensdb-client/singleton";
+import { ensDbWriter } from "@/lib/ensdb/singleton";
 
 const app = new Hono();
 
 // include ENSIndexer Public Config endpoint
 app.get("/config", async (c) => {
-  const publicConfig = await ensDbClient.getEnsIndexerPublicConfig();
+  const publicConfig = await ensDbWriter.getEnsIndexerPublicConfig();
 
   // Invariant: the public config is guaranteed to be available in ENSDb after
   // application startup.
@@ -30,7 +30,7 @@ app.get("/config", async (c) => {
 
 app.get("/indexing-status", async (c) => {
   try {
-    const crossChainSnapshot = await ensDbClient.getIndexingStatusSnapshot();
+    const crossChainSnapshot = await ensDbWriter.getIndexingStatusSnapshot();
 
     // Invariant: the Indexing Status Snapshot is expected to be available in
     // ENSDb shortly after application startup. There is a possibility that

apps/ensindexer/ponder/src/api/index.ts

@@ -5,6 +5,7 @@ import { cors } from "hono/cors";
 
 import type { ErrorResponse } from "@ensnode/ensnode-sdk";
 
+import { migrateEnsNodeSchema } from "@/lib/ensdb/migrate-ensnode-schema";
 import { startEnsDbWriterWorker } from "@/lib/ensdb-writer-worker/singleton";
 
 import ensNodeApi from "./handlers/ensnode-api";
@@ -13,7 +14,14 @@ import ensNodeApi from "./handlers/ensnode-api";
 // the `api` directory of the Ponder app to avoid the following build issue:
 // Error: Invalid dependency graph. Config, schema, and indexing function files
 // cannot import objects from the API function file "src/api/index.ts".
-startEnsDbWriterWorker();
+// Before starting the ENSDb Writer Worker, we need to ensure that
+// the ENSNode Schema in ENSDb is up to date by running any pending migrations.
+migrateEnsNodeSchema()
+  .then(startEnsDbWriterWorker)
+  .catch((error) => {
+    console.error("Failed to migrate ENSNode Schema — ", error);
+    process.exit(1);
+  });
 
 const app = new Hono();