Skip to content

Update /docs/hosted-instances page #2173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tk-o wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update /docs/hosted-instances page #2173

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7c3a8fb
Update `/docs/hosted-instances` page
tk-o May 21, 2026
12f3d03
Merge remote-tracking branch 'origin/main' into docs/update-hosted-in…
tk-o May 21, 2026
1778668
Apply AI PR feedback
tk-o May 21, 2026
28e6450
Improve definition list styling
tk-o May 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ export const integrateSidebarTopic = {
link: "/docs/integrate/integration-options/omnigraph-graphql-api",
},
{
label: "ENSDb Integration Quickstart",
label: "ENSDb (SQL)",
link: "/docs/integrate/integration-options/ensdb",
},
{
Expand All @@ -144,7 +144,7 @@ export const integrateSidebarTopic = {
link: "/docs/integrate/integration-options/ensskills",
},
{
label: "ensdb-cli (Snapshots)",
label: "ensdb-cli (ENSDb Snapshots)",
link: "/docs/integrate/integration-options/ensdb-cli",
},
{
Expand Down
22 changes: 19 additions & 3 deletions docs/ensnode.io/src/components/molecules/HostedEnsNodeInstances.astro
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
---
import ENSAdminLogoDark from "@components/atoms/logos/astro/ENSAdminLogoDark.astro";

const { instanceURL, connectWithENSAdminURL, namespace, plugins, purpose } = Astro.props;
const { instanceURL, connectWithENSAdminURL, namespace, deployments, plugins } = Astro.props;
export const ensNodeVersion = "v1.13.1";
Comment on lines +4 to +5
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const ensNodeVersion = "v1.13.1";
export const hostedEnsNodeVersion = "v1.13.1";

---
<table style={{marginTop: "0"}}>
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rename this UI component / file to be singular: HostedEnsNodeInstance and not the plural HostedEnsNodeInstances.

<tbody>
Expand All @@ -16,18 +17,33 @@ const { instanceURL, connectWithENSAdminURL, namespace, plugins, purpose } = Ast
</a>
</td>
</tr>
<tr>
<td style={{verticalAlign: "middle"}}>ENSNode Version</td>
<td>{ensNodeVersion}</td>
</tr>
<tr>
<td style={{verticalAlign: "middle"}}>ENS Namespace</td>
<td>{namespace}</td>
</tr>
<tr>
<td style={{verticalAlign: "middle"}}>ENS Deployments</td>
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<td style={{verticalAlign: "middle"}}>ENS Deployments</td>
<td style={{verticalAlign: "middle"}}>ENS Versions</td>

<td>{deployments}</td>
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<td>{deployments}</td>
<td>{ensVersions}</td>

Please note: It is not a typo that I wrote this in the plural form. That is correct. It should NOT be singular. This is very important.

</tr>
<tr>
<td>Active Plugins</td>
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<td>Active Plugins</td>
<td>ENSNode Plugins</td>

<td>{plugins}</td>
</tr>
<tr>
<td>Purpose</td>
<td>APIs</td>
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<td>APIs</td>
<td>ENS APIs</td>

<td>
{purpose}
<dl>
<dt>ENS Omnigraph API</dt>
<dd class="pl-0"><slot name="ens-omnigraph-api" /></dd>
<dt>ENS Protocol Acceleration</dt>
<dd class="pl-0"><slot name="ens-protocol-acceleration" /></dd>
<dt>ENS Subgraph API</dt>
<dd class="pl-0"><slot name="ens-subgraph-api" /></dd>
</dl>
</td>
</tr>
</tbody>
Expand Down
2 changes: 1 addition & 1 deletion docs/ensnode.io/src/components/molecules/HostedInstanceSdkVersionWarning.astro
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ const sdkList = isEnskit
---

<Aside type="caution" title="Version compatibility with hosted instances">
Our hosted ENSNode instances currently run ENSNode v1.13. If you are querying them from your own app, you <strong>must</strong> use <span set:html={sdkList} />. The latest published versions (<code>1.14.0+</code>) contain breaking changes in the Omnigraph API data model not yet deployed to our hosted infrastructure. Use these exact install commands:
<a href="/docs/hosted-instances">Our hosted ENSNode instances</a> currently run ENSNode v1.13. If you are querying them from your own app, you <strong>must</strong> use <span set:html={sdkList} />. The latest published versions (<code>1.14.0+</code>) contain breaking changes in the Omnigraph API data model not yet deployed to our hosted infrastructure. Use these exact install commands:
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a href="/docs/hosted-instances">Our hosted ENSNode instances</a> currently run ENSNode v1.13. If you are querying them from your own app, you <strong>must</strong> use <span set:html={sdkList} />. The latest published versions (<code>1.14.0+</code>) contain breaking changes in the Omnigraph API data model not yet deployed to our hosted infrastructure. Use these exact install commands:
<a href="/docs/hosted-instances">Our hosted ENSNode instances</a> currently run ENSNode v1.13. If you are querying them from your own app using <code>enssdk</code> or <code>enskit</code>, you <strong>must</strong> use <span set:html={sdkList} />. The latest published versions of these packages (<code>1.14.0+</code>) contain breaking changes to the Omnigraph API data model which have not been deployed yet to our hosted infrastructure. Use these exact install commands:


Comment on lines 26 to 28
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tk-o Can you please action this feedback from Copilot? Let's please remove any reference to "v1.13" that doesn't also give an explicit patch version number. Ex: Please write something like "v1.13.0" or "v1.13.1" or whatever is appropriate instead.

{isBoth ? (
<pre>npm install enssdk@1.13.1
Expand Down
94 changes: 81 additions & 13 deletions docs/ensnode.io/src/content/docs/docs/hosted-instances.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,23 @@ import { LinkCard } from "@astrojs/starlight/components";
import HostedEnsNodeInstances from "@components/molecules/HostedEnsNodeInstances.astro";
import HostedInstanceSdkVersionWarning from "@components/molecules/HostedInstanceSdkVersionWarning.astro";

export const subgraphCompatibilityApiLevel = `API-level Subgraph Compatibility, where GraphQL APIs are equivalent but a superset of data is being queried and therefore the data returned for some queries may be different.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const subgraphCompatibilityApiLevel = `API-level Subgraph Compatibility, where GraphQL APIs are equivalent but a superset of data is being queried and therefore the data returned for some queries may be different.`;
export const subgraphCompatibilityApiLevel = `**API-level Subgraph Compatibility.** This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API. However, additional plugins have been activated which index a superset of data into the subgraph data model in ENSDb (including Basenames, Lineanames, and 3DNS). This superset of indexed data means that the data returned for some ENS Subgraph API queries may be different. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.`;

export const subgraphCompatibilityFull = `Full Subgraph Compatibility at both the API-level and the data-level. ENSNode can be used as a drop-in replacement for the ENS Subgraph, with guarantees that all data returned by ENSNode will be fully aligned with the ENS Subgraph.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const subgraphCompatibilityFull = `Full Subgraph Compatibility at both the API-level and the data-level. ENSNode can be used as a drop-in replacement for the ENS Subgraph, with guarantees that all data returned by ENSNode will be fully aligned with the ENS Subgraph.`;
export const subgraphCompatibilityFull = `**Full Subgraph Compatibility.** This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API at both the API-level and the data-level. We have exhaustively tested and verified that every data record returned by this ENSNode instance's ENS Subgraph API is byte-for-byte identical with The Graph's ENS Subgraph API. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.`;

export const omnigraphForEnsV1 = `Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2, though data is exclusively sourced from ENSv1. ENSNode can be used as a future-proof integration point for your app to smoothly transition to ENSv2 when you need.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const omnigraphForEnsV1 = `Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2, though data is exclusively sourced from ENSv1. ENSNode can be used as a future-proof integration point for your app to smoothly transition to ENSv2 when you need.`;
export const omnigraphForEnsV1 = `**Activated.** Demonstrates the ENS Omnigraph's ability to support ENSv1 only before ENSv2 launches and both ENSv1 and ENSv2 are concurrently active. Until ENSv2 launches on this namespace, only ENSv1 domains will be available. As soon as ENSv2 launches on this namespace both ENSv1 and ENSv2 domains will be available.`;

export const omnigraphForEnsV1AndEnsV2 = `Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2. When ENSv2 launches in Summer 2026, data from two protocol versions coexist — and the ENS Omnigraph API will keep your app working against both, at the same time, with no code changes. Domains from ENSv1 and ENSv2 are indexed concurrently and exposed through a unified schema.`;
export const omnigraphUnavailable = `Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const omnigraphUnavailable = `Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph.`;
export const omnigraphUnactivated = `**Not activated.** This ENSNode instance optimizes for maximum compatibility with the ENS Subgraph. Therefore it exclusively activates the **subgraph** plugin and does not activate the **unigraph** plugin that the ENS Omnigraph API requires.`;

export const ensProtocolAccelerationAvailable = `Radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const ensProtocolAccelerationAvailable = `Radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains.`;
export const ensProtocolAccelerationAvailable = `**Available.** Accelerate most of your ENS protocol resolution requests while maintaining full compliance with all ENS protocol standards and best practices.`;

Note: It is not an accident that I described this as "Available" rather than "Activated" because the actual activation of protocol acceleration on a specific query has additional factors to consider including worst case distance, etc.

export const ensProtocolAccelerationUnavailable = `Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph.`;
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export const ensProtocolAccelerationUnavailable = `Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph.`;
export const ensProtocolAccelerationUnavailable = `**Unavailable.** Your ENS protocol resolution requests will be serviced in full compliance with all ENS protocol standards and best practices. However, this ENSNode instance did not activate the `protocol-acceleration` plugin and therefore ENS resolution requests will be serviced accurately but without acceleration.`;


## Hosted Instances
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Hosted Instances
## Get Started Quickly


NameHash Labs provides freely available hosted instances for ENS developers looking to get started quickly.
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NameHash Labs provides freely available hosted instances for ENS developers looking to get started quickly.
NameHash Labs provides hosted instances of ENSNode for developers building on ENS and looking to get started quickly.


These instances are provided free of charge with no API key required, have no rate limiting, and are maintained and monitored by the NameHash Labs team.
These instances are currently provided free of charge with no API key required, have no rate limiting, and are maintained and monitored by the NameHash Labs team.

<HostedInstanceSdkVersionWarning for="both" />

### Available instance configurations
### ENS Namespaces

Each ENSNode hosted instance is configured for a specific ENS **namespace** and activated ENSNode **plugins**. The ENS namespace identifies which ENS protocol deployment will be indexed by ENSNode (ex: mainnet or sepolia). The activated plugins determine the specific indexed data model ENSIndexer will produce in ENSDb and therefore which APIs ENSApi will make available to query.
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Each ENSNode hosted instance is configured for a specific ENS **namespace** and activated ENSNode **plugins**. The ENS namespace identifies which ENS protocol deployment will be indexed by ENSNode (ex: mainnet or sepolia). The activated plugins determine the specific indexed data model ENSIndexer will produce in ENSDb and therefore which APIs ENSApi will make available to query.
Each ENSNode instance is configured for a specific **ENS namespace**. An ENS namespace identifies which ENS protocol deployment ENSNode will provide data for (ex: mainnet or sepolia).
Each ENS namespace is associated with a particular ENS Root Registry deployment, which may or may not have completed the transition from ENSv1 (only) to ENSv1 + ENSv2 (both v1 and v2 concurrently activated together).
ENSNode supports all of the following ENS namespaces:
- `mainnet` (currently ENSv1 only and not also ENSv2 yet)
- `sepolia` (currently ENSv1 only and not also ENSv2 yet)
- `sepolia-v2` (now ENSv1 + ENSv2 — An *all new* deployment of ENS to Sepolia that is already upgraded to ENSv1 + ENSv2 and is independent of the traditional `sepolia` ENS namespace listed above which currently remains ENSv1 only)
- `ens-test-env` (now ENSv1 + ENSv2 — A deployment of ENSv1 + ENSv2 to a local Anvil chain for development and testing. For details see https://github.com/ensdomains/ens-test-env and https://github.com/ensdomains/contracts-v2). Teams working on the core ENS protocol and infrastructure such as ENS Labs and NameHash Labs are using this ENSNode configuration to support ENSv2 development.
More details about ENS namespaces can be found inside [ENSNode's datasources package](https://github.com/namehash/ensnode/tree/main/packages/datasources).
### ENSNode Plugins
Each ENSNode instance is also configured for a specific set of activated **ENSNode plugins**.
The activated plugins determine the specific indexed data model and data records ENSIndexer will produce in ENSDb and therefore which APIs and data records ENSApi will make available to query.
### ENSv1 + ENSv2 Instances
These instances are associated with an ENS namespace that has upgraded to ENSv1 + ENSv2 and demonstrate the latest support in ENSNode for ENSv1 and ENSv2 being concurrently activated together.

Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tk-o Please manually delete all the content I've highlighted in this screenshot. Please note how I proposed edits to all of it in the suggestion above, however GitHub didn't allow me to directly propose edits to these lines in the PR review and so need you to manually heal things.

CleanShot 2026-05-22 at 16 53 38


Expand All @@ -43,9 +51,21 @@ The `sepolia-v2` namespace is undergoing active development by the ENS Labs team
instanceURL="https://api.v2-sepolia.ensnode.io"
connectWithENSAdminURL="https://admin.ensnode.io/connection?connection=https%3A%2F%2Fapi.v2-sepolia.ensnode.io"
namespace="sepolia-v2"
plugins="unigraph, protocol-acceleration"
purpose="Demonstration of ENSNode's support for an ENS namespace that has already transitioned to ENSv2."
/>
deployments="(ENSv1+ENSv2)"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
deployments="(ENSv1+ENSv2)"
deployments="ENSv1 + ENSv2 (concurrently activated together)"

plugins="subgraph, unigraph, protocol-acceleration"
>
<Fragment slot="ens-omnigraph-api">
{omnigraphForEnsV1AndEnsV2}
</Fragment>

<Fragment slot="ens-subgraph-api">
{subgraphCompatibilityApiLevel}
</Fragment>

<Fragment slot="ens-protocol-acceleration">
{ensProtocolAccelerationAvailable}
</Fragment>
</HostedEnsNodeInstances>

## ENSv1 Instances
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## ENSv1 Instances
## ENSv1 Only Instances (not also ENSv2 yet)


Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the line below, please change:

"These instances are associated with an ENS namespace that has NOT upgraded to ENSv2 yet and are still operating under ENSv1."

to:

"These instances are associated with an ENS namespace that has NOT upgraded to support ENSv1 and ENSv2 concurrently yet and are still operating exclusively under ENSv1."

Expand All @@ -61,19 +81,43 @@ These ENSNode instances focus on pushing the boundaries of what's possible with
instanceURL="https://api.alpha.ensnode.io"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Several lines above, could you please change:

"These ENSNode instances focus on pushing the boundaries of what's possible with ENSNode."

to:

"These ENSNode instances do not constrain themselves to exclusively activating the subgraph plugin. They activate additional plugins such as the unigraph plugin to demonstrate the latest capabilities of ENSNode including the new ENS Omnigraph API."

connectWithENSAdminURL="https://admin.ensnode.io/connection?connection=https%3A%2F%2Fapi.alpha.ensnode.io"
namespace="mainnet"
deployments="(ENSv1 only)"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
deployments="(ENSv1 only)"
deployments="ENSv1 only (not also ENSv2 yet)"

plugins="subgraph, basenames, lineanames, threedns, unigraph, protocol-acceleration, registrars, tokenscope"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
plugins="subgraph, basenames, lineanames, threedns, unigraph, protocol-acceleration, registrars, tokenscope"
plugins="**unigraph**, **protocol-acceleration**, **subgraph**, basenames, lineanames, threedns, registrars, tokenscope"

purpose="Demonstration of ENSNode's multichain ENS indexing capability for an ENS namespace (mainnet) that is still operating ENSv1. Experience how the ENS Omnigraph API, enssdk, enskit, and the full stack of ENSNode services provide support to developers to become ENSv2 ready even before ENSv2 launches. Provides a superset of the data indexed by the ENS Subgraph. Offers a preview of ENS Protocol Acceleration."
/>
>
<Fragment slot="ens-omnigraph-api">
{omnigraphForEnsV1}
</Fragment>

<Fragment slot="ens-subgraph-api">
{subgraphCompatibilityApiLevel}
</Fragment>

<Fragment slot="ens-protocol-acceleration">
{ensProtocolAccelerationAvailable}
</Fragment>
</HostedEnsNodeInstances>

#### ENSNode 'Alpha-Sepolia'

<HostedEnsNodeInstances
instanceURL="https://api.alpha-sepolia.ensnode.io"
connectWithENSAdminURL="https://admin.ensnode.io/connection?connection=https%3A%2F%2Fapi.alpha-sepolia.ensnode.io"
namespace="sepolia"
deployments="(ENSv1 only)"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
deployments="(ENSv1 only)"
deployments="ENSv1 only (not also ENSv2 yet)"

plugins="subgraph, basenames, lineanames, registrars, unigraph, protocol-acceleration"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
plugins="subgraph, basenames, lineanames, registrars, unigraph, protocol-acceleration"
plugins="**unigraph**, **protocol-acceleration**, **subgraph**, basenames, lineanames, registrars"

purpose="Demonstration of ENSNode's multichain ENS indexing capability for an ENS namespace (sepolia) that is still operating ENSv1. Experience how the ENS Omnigraph API, enssdk, enskit, and the full stack of ENSNode services provide support to developers to become ENSv2 ready even before ENSv2 launches. Provides a superset of the data indexed by the ENS Subgraph. Offers a preview of ENS Protocol Acceleration."
/>
>
<Fragment slot="ens-omnigraph-api">
{omnigraphForEnsV1}
</Fragment>

<Fragment slot="ens-subgraph-api">
{subgraphCompatibilityApiLevel}
</Fragment>

<Fragment slot="ens-protocol-acceleration">
{ensProtocolAccelerationAvailable}
</Fragment>
</HostedEnsNodeInstances>

### Subgraph-style Deployments

Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change the line below from:

"These ENSNode instances focus on maximizing backwards compatibility with the ENS Subgraph."

to:

"These ENSNode instances focus on maximizing backwards compatibility with the ENS Subgraph. Therefore they exclusively activate the subgraph plugin and no others."

Expand All @@ -85,19 +129,43 @@ These ENSNode instances focus on maximizing backwards compatibility with the ENS
instanceURL="https://api.mainnet.ensnode.io"
connectWithENSAdminURL="https://admin.ensnode.io/connection?connection=https%3A%2F%2Fapi.mainnet.ensnode.io"
namespace="mainnet"
deployments="(ENSv1 only)"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
deployments="(ENSv1 only)"
deployments="ENSv1 only (not also ENSv2 yet)"

plugins="subgraph"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
plugins="subgraph"
plugins="**subgraph**"

purpose="Demonstration of ENSNode's backwards compatibility with the ENS Subgraph. Provides 1:1 Subgraph compatible data on mainnet."
/>
>
<Fragment slot="ens-omnigraph-api">
{omnigraphUnavailable}
</Fragment>

<Fragment slot="ens-subgraph-api">
{subgraphCompatibilityFull}
</Fragment>

<Fragment slot="ens-protocol-acceleration">
{ensProtocolAccelerationUnavailable}
</Fragment>
</HostedEnsNodeInstances>

#### ENSNode 'Sepolia'

<HostedEnsNodeInstances
instanceURL="https://api.sepolia.ensnode.io"
connectWithENSAdminURL="https://admin.ensnode.io/connection?connection=https%3A%2F%2Fapi.sepolia.ensnode.io"
namespace="sepolia"
deployments="(ENSv1 only)"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
deployments="(ENSv1 only)"
deployments="ENSv1 only (not also ENSv2 yet)"

plugins="subgraph"
Copy link
Copy Markdown
Member

@lightwalker-eth lightwalker-eth May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
plugins="subgraph"
plugins="**subgraph**"

purpose="Demonstration of ENSNode's backwards compatibility with the ENS Subgraph. Provides 1:1 Subgraph compatible data on Sepolia."
/>
>
<Fragment slot="ens-omnigraph-api">
{omnigraphUnavailable}
</Fragment>

<Fragment slot="ens-subgraph-api">
{subgraphCompatibilityFull}
</Fragment>

<Fragment slot="ens-protocol-acceleration">
{ensProtocolAccelerationUnavailable}
</Fragment>
</HostedEnsNodeInstances>

## Start building

Expand Down
Loading