From a0bd49ae11582c8191f1ee1b771007da651b841b Mon Sep 17 00:00:00 2001 From: Tomasz Kopacki Date: Tue, 9 Jun 2026 11:22:57 +0200 Subject: [PATCH 1/3] Update term to "live push notifications" --- .../starlight/sidebar-topics/integrate.ts | 2 +- .../src/content/docs/docs/integrate/index.mdx | 2 +- .../integrate/integration-options/ensengine.mdx | 16 ++++++---------- .../docs/docs/services/ensengine/index.mdx | 6 +++--- 4 files changed, 11 insertions(+), 15 deletions(-) diff --git a/docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts b/docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts index bcfd7d91a..9d084e8e0 100644 --- a/docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts +++ b/docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts @@ -196,7 +196,7 @@ export const integrateSidebarTopic = { link: "/docs/integrate/integration-options/ensdb-cli", }, { - label: "ENSEngine (Webhooks)", + label: "ENSEngine (Push notifications)", link: "/docs/integrate/integration-options/ensengine", }, ], diff --git a/docs/ensnode.io/src/content/docs/docs/integrate/index.mdx b/docs/ensnode.io/src/content/docs/docs/integrate/index.mdx index d34a04a3c..92ee6f6f5 100644 --- a/docs/ensnode.io/src/content/docs/docs/integrate/index.mdx +++ b/docs/ensnode.io/src/content/docs/docs/integrate/index.mdx @@ -208,7 +208,7 @@ Beyond [`enssdk`](/docs/integrate/integration-options/enssdk), [`enskit`](/docs/ - **[enscli (CLI)](/docs/integrate/integration-options/enscli)** — resolve names, look up records, and run ad-hoc Omnigraph queries from the terminal — built for humans and AI agents alike. - **[ensskills (AI agents)](/docs/integrate/integration-options/ensskills)** — a curated set of skills that gives AI coding agents a well-defined contract for working with ENS. - **[ensdb-cli (ENSDb Snapshots)](/docs/integrate/integration-options/ensdb-cli)** — bootstrap a fresh ENSDb in minutes from portable, versioned snapshots instead of waiting days on a full historical backfill. -- **[ENSEngine (Webhooks)](/docs/integrate/integration-options/ensengine)** — subscribe to ENS-aware webhooks driven by changes in ENSDb, so your apps can stop polling and start reacting. +- **[ENSEngine (Live push notifications)](/docs/integrate/integration-options/ensengine)** — subscribe to ENS-aware live notifications driven by changes in ENSDb, so your apps can stop polling and start reacting. - ENS-native event-driven reactive development (such as webhooks) is coming soon with + ENS-native event-driven reactive development is coming soon with [ENSEngine](/docs/services/ensengine) that builds on top of [ENSDb](/docs/services/ensdb). @@ -19,16 +19,12 @@ Today, if you want your app to react to ENS state changes, you have two unappeal ## What we're building -ENSEngine will be an **ENS-native event-driven reactive development service** (for webhooks and more) so your app can subscribe to ENS state changes in ENSDb the same way you'd subscribe to a Stripe or GitHub webhook - except the events speak the language of discrete meaningful ENS actions, not the language of bare-metal raw onchain event transaction logs. - -```http title="example-webhook.http" -POST https://your-app.example.com/webhooks/ens -Content-Type: application/json +ENSEngine will be an **ENS-native event-driven reactive development service** (for live push notifications) so your app can subscribe to ENS state changes in ENSDb the same way you'd subscribe to updates from Stripe or GitHub - except the events speak the language of discrete meaningful ENS actions, not the language of bare-metal raw onchain event transaction logs. +```json title="example-event.json" { "type": "domain.transferred", - "name": "vitalik.eth", - ... + "name": "vitalik.eth" } ``` diff --git a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx index 622bd1511..5c207dfdb 100644 --- a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx +++ b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx @@ -1,6 +1,6 @@ --- title: ENSEngine -description: Coming soon - the ENSNode service for push-based, reactive ENS functionality. Watches your ENSDb for changes and turns them into ENS-aware webhooks. +description: Coming soon - the ENSNode service for push-based, reactive ENS functionality. Watches your ENSDb for changes and turns them into ENS-aware push notifications. sidebar: label: Overview order: 1 @@ -20,7 +20,7 @@ Today, building an app that reacts to ENS - when an avatar changes, when a name ## What it is -ENSEngine is the part of ENSNode that **watches your ENSDb for changes in real time and delivers ENS-aware events** - including webhooks - to any sink you configure. +ENSEngine is the part of ENSNode that **watches your ENSDb for changes in real time and delivers ENS-aware events** to any sink you configure. It sits alongside [ENSIndexer](/docs/services/ensindexer), [ENSDb](/docs/services/ensdb), [ENSRainbow](/docs/services/ensrainbow), [ENSApi](/docs/services/ensapi), and [ENSAdmin](/docs/services/ensadmin) as the home for reactive / event-based functionality across the ENSNode stack. @@ -49,7 +49,7 @@ The internal pipeline is intentionally simple to describe: - **Enrich** - attach ENS-level context to raw changes so consumers don't have to. - **Filter** - apply subscription rules so each sink only sees events it cares about. - **Transform** - shape events into the right payload for each sink type. -- **Route** - deliver to webhooks, cache-invalidation hooks, database sync targets, notification systems, and more. +- **Dispatch** - deliver to webhooks, cache-invalidation hooks, database sync targets, notification systems, and more. Implementation details behind the watch layer are intentionally not part of this teaser. Those will land in dedicated docs when the service ships. From 487b5467c497c600d6770c1919aa3a4c59225703 Mon Sep 17 00:00:00 2001 From: Tomasz Kopacki Date: Tue, 9 Jun 2026 12:34:39 +0200 Subject: [PATCH 2/3] Apply PR feedback --- .../src/content/docs/docs/services/ensengine/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx index 5c207dfdb..82c1a51f9 100644 --- a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx +++ b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx @@ -1,6 +1,6 @@ --- title: ENSEngine -description: Coming soon - the ENSNode service for push-based, reactive ENS functionality. Watches your ENSDb for changes and turns them into ENS-aware push notifications. +description: Coming soon - the ENSNode service for push-based, reactive ENS functionality. Watches your ENSDb for changes and turns them into ENS-aware live push notifications. sidebar: label: Overview order: 1 From 99aab9d25a66a33e55b095b51b951ef33ec2ff00 Mon Sep 17 00:00:00 2001 From: Tomek Kopacki Date: Tue, 9 Jun 2026 14:11:03 +0200 Subject: [PATCH 3/3] Apply suggestion from @tk-o --- .../src/content/docs/docs/services/ensengine/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx index 82c1a51f9..9e768c279 100644 --- a/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx +++ b/docs/ensnode.io/src/content/docs/docs/services/ensengine/index.mdx @@ -49,7 +49,7 @@ The internal pipeline is intentionally simple to describe: - **Enrich** - attach ENS-level context to raw changes so consumers don't have to. - **Filter** - apply subscription rules so each sink only sees events it cares about. - **Transform** - shape events into the right payload for each sink type. -- **Dispatch** - deliver to webhooks, cache-invalidation hooks, database sync targets, notification systems, and more. +- **Route** - deliver to webhooks, cache-invalidation hooks, database sync targets, notification systems, and more. Implementation details behind the watch layer are intentionally not part of this teaser. Those will land in dedicated docs when the service ships.