feat(ponder-ens): introduce plugin architecture

.env.local.example

@@ -0,0 +1,15 @@
+# RPC urls, follow the format RPC_URL_{chainId}={rpcUrl}
+
+PONDER_RPC_URL_1=https://ethereum-rpc.publicnode.com
+PONDER_RPC_URL_8453=https://base-rpc.publicnode.com
+PONDER_RPC_URL_59144=https://linea-rpc.publicnode.com
+
+# ponder indexer ens deployment configuration
+
+ENS_DEPLOYMENT_CHAIN_ID=1
+
+# ponder indexer database configuration
+
+## one schema name per chain ID, i.e. ponder_ens_${ENS_DEPLOYMENT_CHAIN_ID}
+DATABASE_SCHEMA=ponder_ens_1
+DATABASE_URL=postgresql://dbuser:abcd1234@localhost:5432/my_database

ponder.config.ts

@@ -1,11 +1,25 @@
 import { createConfig } from "ponder";
-import { config as ethereumConfig} from "./src/ponder-ens-plugins/ethereum/ponder.config";
+import { config as baseConfig } from "./src/ponder-ens-plugins/base/ponder.config";
+import { config as ethereumConfig } from "./src/ponder-ens-plugins/ethereum/ponder.config";
+
+console.log({
+  networks: {
+    ...baseConfig.networks,
+    ...ethereumConfig.networks,
+  },
+  contracts: {
+    ...baseConfig.contracts,
+    ...ethereumConfig.contracts,
+  },
+})
 
 export default createConfig({
   networks: {
+    ...baseConfig.networks,
     ...ethereumConfig.networks,
   },
   contracts: {
+    ...baseConfig.contracts,
     ...ethereumConfig.contracts,
   },
 });

src/lib/ens-helpers.ts

@@ -3,6 +3,7 @@ import { type Hex, concat, keccak256, namehash, toHex } from "viem";
 // TODO: pull from ens utils lib or something
 export const NAMEHASH_ZERO = namehash("");
 export const NAMEHASH_ETH = namehash("eth");
+export const NAMEHASH_BASE_ETH = namehash("base.eth");
 
 // TODO: this should probably be a part of some ens util lib
 export const makeSubnodeNamehash = (node: Hex, label: Hex) => keccak256(concat([node, label]));

src/ponder-ens-plugins/base/README.md

@@ -0,0 +1,9 @@
+# Base ENS plugin for Ponder indexer
+
+This plugin contains configuration required to run blockchain indexing with [the Ponder app](https://ponder.sh/). It includes relevant ABI files, contract addresses and the block numbers those contracts were deployed at on a selected network.
+
+## Architecture
+
+The Base implementation for ENS protocol has custom naming convention, which was described here:
+https://github.com/base-org/basenames?tab=readme-ov-file#architecture
+