isolated chain ordering

.changeset/config.json

@@ -2,7 +2,15 @@
   "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
   "changelog": ["@changesets/changelog-github", { "repo": "ponder-sh/ponder" }],
   "commit": false,
-  "fixed": [["ponder", "create-ponder", "eslint-config-ponder"]],
+  "fixed": [
+    [
+      "ponder",
+      "create-ponder",
+      "eslint-config-ponder",
+      "@ponder/client",
+      "@ponder/react"
+    ]
+  ],
   "ignore": [
     "@ponder/common",
     "ponder-examples-feature-accounts",

.changeset/pre.json

@@ -0,0 +1,13 @@
+{
+  "mode": "pre",
+  "tag": "next",
+  "initialVersions": {
+    "@ponder/client": "0.0.0",
+    "@ponder/common": "0.0.0",
+    "ponder": "0.8.7",
+    "create-ponder": "0.8.7",
+    "eslint-config-ponder": "0.8.7",
+    "@ponder/utils": "0.2.3"
+  },
+  "changesets": []
+}

.changeset/warm-cats-march.md

@@ -0,0 +1,8 @@
+---
+"create-ponder": minor
+"@ponder/client": minor
+"@ponder/react": minor
+"ponder": minor
+---
+
+Released `0.9`. Visit the [migration guide](https://ponder.sh/docs/migration-guide) for details.

.github/workflows/main.yml

@@ -21,15 +21,6 @@ jobs:
       - name: Setup
         uses: ./.github/actions/setup
 
-      - name: Codegen
-        run: cd packages/core/ && pnpm wagmi generate
-
-      - name: Typecheck
-        run: pnpm typecheck
-
-      - name: Test (types)
-        run: pnpm --filter "ponder" test:typecheck
-
       - name: Lint
         run: pnpm lint
 
@@ -46,6 +37,9 @@ jobs:
       - name: Build
         run: pnpm build
 
+      - name: Test (types)
+        run: pnpm --filter "ponder" test:typecheck
+
   test:
     name: Test [core]
     runs-on: ubuntu-latest
@@ -66,9 +60,6 @@ jobs:
       - name: Setup
         uses: ./.github/actions/setup
 
-      - name: Codegen
-        run: cd packages/core/ && pnpm wagmi generate
-
       - name: Test
         run: pnpm --filter "ponder" test
         env:

.github/workflows/windows.yml

@@ -26,9 +26,6 @@ jobs:
       - name: Setup
         uses: ./.github/actions/setup
 
-      - name: Codegen
-        run: cd packages/core/ && pnpm wagmi generate
-
       - name: Test
         run: pnpm --filter "ponder" test
         env:

biome.json

@@ -17,7 +17,8 @@
       "docs/",
       "benchmarks/apps/subgraph-*",
       "pnpm-lock.yaml",
-      "**/*.sol"
+      "**/*.sol",
+      "tsconfig.base.json"
     ]
   },
   "formatter": {

docs/pages/docs/api-reference/database.mdx

@@ -76,6 +76,10 @@ style Z2 fill:#f00,color:#fff
 
 The `_ponder_meta` table tracks the state of an instance running in a specific database schema. It stores the `build_id`, indexing checkpoint, and table names of the current instance, and uses a heartbeat locking mechanism to support the lifecycle logic described above.
 
+### Status Table
+
+The `_ponder_status` table tracks the indexing progress of each chain.
+
 ### Build ID and crash recovery
 
 During the build step, each instance generates a content hash of the entire app (config, schema, and indexing function file contents). This is called the `build_id`.

docs/pages/docs/api-reference/ponder-cli.mdx

@@ -28,7 +28,7 @@ Commands:
   start [options]        Start the production server
   serve [options]        Start the production HTTP server without the indexer
   db list                List all deployments
-  codegen                Generate the schema.graphql file, then exit
+  codegen                Generate the ponder-env.d.ts file, then exit
 ```
 
 ## dev
@@ -110,12 +110,12 @@ List all deployments
   when changes are detected in `ponder.schema.ts`.
 </Callout>
 
-Generate the `schema.graphql` file.
+Generate the `ponder-env.d.ts` file.
 
 ```bash
 Usage: ponder codegen [options]
 
-Generate the schema.graphql file, then exit
+Generate the ponder-env.d.ts file, then exit
 
 Options:
   -h, --help  display help for command

docs/pages/docs/contracts-and-networks.mdx

@@ -477,49 +477,10 @@ Tip: On Etherscan, there is a link to the current implementation contract on the
 
 ## Event filter
 
-The `filter` option filters for events by signature and indexed argument values. This makes it possible to index events emitted by _any contract on the network_ that match the specified signature and arguments.
-
-### By event name or signature
-
-The `filter.event` option accepts an event name (or list of event names) present in the provided ABI.
-
-```ts filename="ponder.config.ts" {14}
-import { createConfig } from "ponder";
-import { http } from "viem";
-
-import { ERC20Abi } from "./abis/ERC20";
-
-export default createConfig({
-  networks: {
-    mainnet: { chainId: 1, transport: http(process.env.PONDER_RPC_URL_1) },
-  },
-  contracts: {
-    ERC20: {
-      abi: ERC20Abi,
-      network: "mainnet",
-      filter: { event: "Transfer" },
-      //        ^? "Transfer" | "Approval" | ("Transfer" | "Approval")[]
-      startBlock: 18500000,
-      endBlock: 18505000,
-    },
-  },
-});
-```
-
-The indexing functions you write will run for all events matching the filter, regardless of which contract emitted them.
-
-```ts filename="src/index.ts"
-import { ponder } from "ponder:registry";
-
-ponder.on("ERC20:Transfer", async ({ event }) => {
-  // This is the address of the contract that emitted the event.
-  // With this config, it could be any ERC20 contract on mainnet.
-  event.log.address;
-  //        ^? string
-});
-```
-
-### By indexed argument value
+<Callout type="info">
+  Ponder will automatically filter out event signatures that don't have a
+  registered indexing function.
+</Callout>
 
 You can use the `filter.event` and `filter.args` options together to filter for events that have specific indexed argument values. Each indexed argument field accepts a single value or a list of values to match.
 
@@ -569,6 +530,10 @@ ponder.on("ERC20:Transfer", async ({ event }) => {
 });
 ```
 
+<Callout type="info">
+  Multiple filters can be specified by passing an array of filter objects.
+</Callout>
+
 ## Call traces
 
 The `includeCallTraces{:ts}` option specifies whether to enable call trace indexing for a contract. By default, call traces are **disabled**.

docs/pages/docs/migration-guide.mdx

@@ -7,6 +7,122 @@ import { FileTree, Steps, Tabs, Callout } from "nextra/components";
 
 # Migration guide
 
+## 0.9
+
+### API functions
+
+This release makes Ponder's API layer less opinionated. Now, you just need to default export a Hono `App` object from the `src/api/index.ts` file, and Ponder will serve it.
+
+<Callout type="warning">
+  The `src/api/index.ts` file is now required and no GraphQL endpoint is served
+  by default.
+</Callout>
+
+Copy the following code into `src/api/index.ts` to achieve the same functionality as `<=0.8`.
+
+```ts filename="src/api/index.ts"
+import { db } from "ponder:api";
+import schema from "ponder:schema";
+import { Hono } from "hono";
+import { graphql } from "ponder";
+
+const app = new Hono();
+
+app.use("/", graphql({ db, schema }));
+app.use("/graphql", graphql({ db, schema }));
+
+export default app;
+```
+
+#### Removed `ponder.get()`, `post()`, `use()`
+
+Now, simply use Hono's built-in routing system.
+
+<div className="code-columns">
+
+```ts filename="src/api/index.ts (<=0.8)"
+import { ponder } from "ponder:registry";
+
+ponder.get("/hello", (c) => {
+  return c.text("Hello, world!");
+});
+```
+
+```ts filename="src/api/index.ts (0.9)"
+import { Hono } from "hono";
+
+const app = new Hono();
+
+app.get("/hello", (c) => {
+  return c.text("Hello, world!");
+});
+
+export default app;
+```
+
+</div>
+
+#### `import { db } from "ponder:api"`
+
+The `c.db` object was removed from the Hono context. Now, use the `"ponder:api"` virtual module to access a readonly Drizzle database object.
+
+```ts filename="src/api/index.ts" {1,10}
+import { db } from "ponder:api";
+import schema from "ponder:schema";
+import { Hono } from "hono";
+
+const app = new Hono();
+
+app.get("/account/:address", async (c) => {
+  const address = c.req.param("address");
+
+  const account = await db
+    .select()
+    .from(schema.accounts)
+    .where(eq(schema.accounts.address, address))
+    .limit(1);
+
+  return c.json(account);
+});
+
+export default app;
+```
+
+#### `import { publicClients } from "ponder:api"`
+
+[Viem Public Clients](https://viem.sh/docs/clients/public) for each network defined in `ponder.config.ts` are injected into `src/api/index.ts`.
+
+```ts filename="src/api/index.ts" {1,11}
+import { publicClients, db } from "ponder:api";
+import schema from "ponder:schema";
+import { Hono } from "hono";
+
+const app = new Hono();
+
+app.get("/account/:chainId/:address", async (c) => {
+  const chainId = c.req.param("chainId");
+  const address = c.req.param("address");
+
+  const balance = await publicClients[chainId].getBalance({ address });
+
+  const account = await db.query.accounts.findFirst({
+    where: eq(schema.accounts.address, address),
+  });
+
+  return c.json({ balance, account });
+});
+
+export default app;
+```
+
+### `@ponder/client` and `@ponder/react`
+
+Two new packages for querying Ponder apps. [Read more](/docs/query/client).
+
+### Event filters
+
+The `contracts.filter` property now supports multiple filters, and requires argument values. [Read more](/docs/contracts-and-networks#event-filter).
+
 ## 0.8
 
 <Callout type="warning">

docs/pages/docs/query/_meta.ts

@@ -1,5 +1,6 @@
 export default {
-  "graphql": "GraphQL",
   "api-functions": "API functions",
+  "client": "Client",
+  "graphql": "GraphQL",
   "direct-sql": "Direct SQL",
 };