feat(ensapi): implement Registrar Actions API by tk-o · Pull Request #1265 · namehash/ensnode

tk-o · 2025-11-07T19:23:21Z

Scope

implement HTTP route for Registrar Actions API

Sample response

{
  "responseCode": "ok",
  "registrarActions": [
    {
      "id": "176279354400000000111551110000000009601035000000000000012750000000000000184",
      "type": "registration",
      "incrementalDuration": 31536000,
      "registrant": "0x168a4ac73c7d8ac6d1cd56a36d94a4d91825dc68",
      "registrationLifecycle": {
        "subregistry": {
          "subregistryId": "eip155:11155111:0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85",
          "node": "0x93cdeb708b7545dc668eb9280176169d1c33cfd8ed6f04690a0bcc88a93fc4ae"
        },
        "node": "0x5d54aa7328d700144737df21f6ea5d211b84331fa848195bcb4f9853c0b6d1a0",
        "expiresAt": 1794329544,
        "domain": {
          "subname": "undersystem",
          "name": "undersystem.eth"
        }
      },
      "pricing": {
        "baseCost": {
          "currency": "ETH",
          "amount": "3125000000003490"
        },
        "premium": {
          "currency": "ETH",
          "amount": "0"
        },
        "total": {
          "currency": "ETH",
          "amount": "3125000000003490"
        }
      },
      "referral": {
        "encodedReferrer": null,
        "decodedReferrer": null
      },
      "block": {
        "number": 9601035,
        "timestamp": 1762793544
      },
      "transactionHash": "0x08aa690fd7baab1e815da63773cbda3780f4414ef362aae6dbcf053c594fe808",
      "eventIds": [
        "176279354400000000111551110000000009601035000000000000012750000000000000184",
        "176279354400000000111551110000000009601035000000000000012750000000000000196"
      ]
    }
  ]
}

implement ENSNode SDK Client method for the HTTP route from above

Sample client calls

import {
  buildRegistrarActionsFilterForParentName,
  ENSNodeClient,
} from "@ensnode/ensnode-sdk";

const client: ENSNodeClient;

// get latest 25 registrar action records across all indexed subregistries
const registrarActions = await client.registrarActions();

// get latest 5 registrar action records across all indexed subregistries
const registrarActions = await client.registrarActions({
  limit: 5,
});

// get latest 25 registrar action records associated with subregistry managing `eth` name
await client.registrarActions({
  filter: buildRegistrarActionsFilterForParentName('eth'),
});

// get latest 10 registrar action records associated with subregistry managing `base.eth` name
await client.registrarActions({
  filter: buildRegistrarActionsFilterForParentName('base.eth'),
  limit: 10
});

Suggested review order

ENSNode SDK

shared module updates
- packages/ensnode-sdk/src/shared/*
registrar module updates
- packages/ensnode-sdk/src/registrars/*
api module updates
- packages/ensnode-sdk/src/api/*
client module update
- registrarActions() method was introduced, allows filtering by parent name

ENSNode Schema

registrar schema updates
- packages/ensnode-schema/src/schemas/registrars.schema.ts

ENSApi

lib module updates
- apps/ensapi/src/lib/*
handlers module updates
- apps/ensapi/src/handlers/registrar-actions-api.ts

Replaces:

feat: Registrar Actions API integration #1242

Resolves:

Create HTTP API Route for fetching latest registrations #1229

Also includes related serialization functionality.

Introduces a new HTTP route at `GET /api/registrar-actions/latest` which allows fetching the latest "logical registrar actions", including domain information.

changeset-bot · 2025-11-07T19:23:25Z

🦋 Changeset detected

Latest commit: 3415c85

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 14 packages

Name	Type
@ensnode/ensnode-sdk	Minor
@docs/ensnode	Minor
@ensnode/ensnode-schema	Minor
ensapi	Minor
ensadmin	Minor
ensindexer	Minor
ensrainbow	Minor
@ensnode/ensnode-react	Minor
@ensnode/ensrainbow-sdk	Minor
@ensnode/datasources	Minor
@ensnode/ponder-metadata	Minor
@ensnode/ponder-subgraph	Minor
@ensnode/shared-configs	Minor
@docs/ensrainbow	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

vercel · 2025-11-07T19:23:26Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
admin.ensnode.io	Ready	Preview	Comment	Nov 13, 2025 9:25am
ensnode.io	Ready	Preview	Comment	Nov 13, 2025 9:25am
ensrainbow.io	Ready	Preview	Comment	Nov 13, 2025 9:25am

…ction-ens-api

Take domain data model away from registrar actions data model. This help keeping types simple, and still enable clients to get data about registration lifecycle domain in an easy way.

lightwalker-eth

@tk-o Thanks for advancing this. Reviewed and shared feedback 👍

lightwalker-eth · 2025-11-10T07:05:28Z

apps/ensapi/src/handlers/registrar-actions-api.ts

+/**
+ * Latest Registrar Actions
+ */
+app.get("/latest", async (c) => {


Suggested change

/**

* Latest Registrar Actions

*/

app.get("/latest", async (c) => {

/**

* Get Registrar Actions

*/

app.get("/", async (c) => {

Idea: Implement this API so that it implicitly defaults to a sort that returns the latest, but isn't explicitly called "latest".

lightwalker-eth · 2025-11-10T07:08:22Z

apps/ensapi/src/handlers/registrar-actions-api.ts

+const MAX_REALTIME_DISTANCE: Duration = 10 * 60; // 10 minutes in seconds
+
+// inject c.var.isRealtime derived from MAX_REALTIME_DISTANCE
+app.use(makeIsRealtimeMiddleware("registrar-actions-api", MAX_REALTIME_DISTANCE));
+// 404 if Registrar Actions API routes cannot be served over HTTP
+app.use(requireRegistrarActionsPluginMiddleware());


Am I correct to understand this will mean that if our production ENSNode instance becomes more than 10 minutes beyond realtime this API will start returning 404 errors and therefore cause the landing pages we're building on ENSAwards to break?

We need to fix the strategy here. It's wrong to proactively and FORCEFULLY break client-side apps just because we aren't sufficiently realtime. Client side apps are given all the tools they need to decide for themselves how to handle such a case. Why are we forcing this upon them?

lightwalker-eth · 2025-11-10T07:13:43Z

packages/ensnode-sdk/src/registrars/registration-lifecycle.ts

+  /**
+   * Subname
+   *
+   * A child name like `sub.name.eth`, whose parent is `name.eth`.
+   */
+  subname: InterpretedLabel;


Am I correct to assume there's another key idea that's missing in the naming and documentation of this field?

Yes, this is a subname, but more specifically in the context of RegistrationLifecycleDomain isn't it the subname that the registration lifecycle is associated with?

lightwalker-eth · 2025-11-10T07:15:13Z

packages/ensnode-sdk/src/registrars/registrar-action.ts

 /**
 * Globally unique, deterministic ID of an indexed onchain event.
 */
-type RegistrarActionEventId = string;
+export type RegistrarActionEventId = string;


The JSDocs suggest this type should be for ANY indexed onchain event, but the name of this type suggests it is only for a specific subset of indexed onchain events (those associated with Registrar Actions).

Which is it?

lightwalker-eth · 2025-11-10T07:19:19Z

packages/ensnode-sdk/src/api/types.ts

+  registrarActions: RegistrarAction[];
+  registrationLifecycleDomains: Record<Node, RegistrationLifecycleDomain>;


We need to refactor the data model here so that each value returned in the registrarActions field should include the fields currently inside RegistrationLifecycleDomain.

The issue here is that we're too tightly connecting the indexed data model (the data model in Postgres) with the data model returned via the API. This is not the correct path.

The data model returned via the API needs to be an abstraction on top of the data model in Postgres that is optimized for API consumption.

The current design here is definitely not optimized for API consumption.

apps/ensapi/src/lib/middleware/require-registrar-actions-plugins..middleware.ts

lightwalker-eth · 2025-11-10T07:31:02Z

apps/ensapi/src/handlers/registrar-actions-api.ts

+      ({ registrationLifecycle }) => registrationLifecycle.node,
+    );
+    // 2. b) Find the associated Registrar Lifecycle Domain info.
+    const registrationLifecycleDomains =


Red flag here.

This looks like a single query to this API endpoint is performing N queries to the database. Why?

A single query to this API endpoint should relate to exactly 1 query to the database, where that query performs the necessary joins and where the data model we're building in memory is a distinct abstraction from the data model in the database.

lightwalker-eth · 2025-11-10T07:33:12Z

apps/ensapi/src/lib/registrar-actions/find-registration-lifecycle-domians.ts

+ * @param nodes is array containing a list of nodes.
+ * @returns Registration Lifecycle Domains for nodes.
+ */
+export async function findRegistrationLifecycleDomains(


This should not be a distinct operation.

The ideas here should be merged into findRegistrarActions such that it performs the appropriate database joins.

We need our in-memory data model to be optimized for use in-memory. Therefore it needs to be a distinct abstraction on top of the data model in the database.

apps/ensapi/src/lib/registrar-actions/find-registrar-actions.ts

…ponse Clients calling the API will have a complete piece of information about each Registrar Action result handy.

Implement client method for the Registrar Actions API. Also, optimizes the Registrar Actions HTTP route for DB calls. Additionally, allows filterning Registrar Action by subregistry node (which on the client call is refered to as "parent node filter").

…chema to store hex values.

…API.

lightwalker-eth

@tk-o Hey great to see the work here. Reviewed and shared feedback 👍

packages/ensnode-sdk/src/api/types.ts

lightwalker-eth · 2025-11-11T08:18:14Z

packages/ensnode-sdk/src/api/types.ts

+};
+
+/**
+ * A status code for indexing status responses.


Need to update this comment.

lightwalker-eth · 2025-11-11T08:24:11Z

packages/ensnode-sdk/src/client.ts

+   *
+   * const client: ENSNodeClient;
+   *
+   * // get latest 25 registrar action records across all indexed subregistries


Suggest to look for other places where it would be relevant to document how this defaults to 25.

I think I should replace the concrete count with a reference to the const defined in ENSApi. The const value might change, but the reference will stay.

lightwalker-eth · 2025-11-11T08:25:44Z

packages/ensnode-sdk/src/client.ts

+      try {
+        errorResponse = deserializeErrorResponse(responseData);
+      } catch {
+        // if errorResponse is could not be determined,


Suggested change

// if errorResponse is could not be determined,

// if errorResponse could not be determined,

lightwalker-eth · 2025-11-11T08:36:06Z

apps/ensapi/src/lib/registrar-actions/find-registrar-actions.ts

+      eq(schema.registrationLifecycles.node, schema.subgraph_domain.id),
+    )
+    // join Subregistries associated with Registration Lifecycles
+    .innerJoin(


Should this query only conditionally involve the subregistries table when a filter by subregistry is part of the query?

Please ignore this comment if not relevant.

lightwalker-eth · 2025-11-11T10:29:22Z

apps/ensapi/src/lib/registrar-actions/find-registrar-actions.ts

+    timestamp: bigIntToNumber(record.registrarActions.timestamp),
+  } satisfies BlockRef;
+
+  // build the result referencing the "logical registrar action"


Suggested change

// build the result referencing the "logical registrar action"

// build the resulting "logical registrar action"

lightwalker-eth · 2025-11-11T10:52:19Z

packages/ensnode-sdk/src/api/types.ts

+ */
+export type RegistrarActionsResponseOk = {
+  responseCode: typeof RegistrarActionsResponseCodes.Ok;
+  registrarActions: RegistrarActionWithDomain[];


I was really confused trying to unpack all the inheritance in the current data model for RegistrarActionWithDomain.

In my mind the response data model should simply be defined as something like the following.

// NOTE: I see no need for any inheritance at all in our response data model. export interface NamedRegistrarAction { // NOTE: `action.lifecycle` is already a `RegistrationLifecycle`. There's // no need to include multiple copies of a `RegistrationLifecycle` in the response object. action: RegistrarAction; // NOTE: // 1. We don't need a full `RegistrationLifecycleDomain` here, just the `name` // associated with the `RegistrarAction`. There's no need or benefit of including // the `subname` field from the `RegistrationLifecycleDomain` here. // 2. We can simply document an invariant in this object for this `name` field that // it is guaranteed that `namehash(name)` is equal to `action.registrationLifecycle.node` // when using an "encoded labelhash aware" implementation of `namehash` such as the // `namehash` implementation in `viem`. name: InterpretedName; }

... and then of course to still wrap an array of this type using a separate RegistrarActionsResponseOk type which would include the responseCode, etc.

lightwalker-eth · 2025-11-11T10:56:24Z

docs/ensnode.io/src/content/docs/docs/usage/api.mdx

+Track all "logical registrar actions" performed by users across multiple
+subregistries with the Registrar Actions API. This endpoint returns a list


Suggested change

Track all "logical registrar actions" performed by users across multiple

subregistries with the Registrar Actions API. This endpoint returns a list

Query the "logical registrar actions" performed on indexed

subregistries with the Registrar Actions API. This endpoint returns a list

lightwalker-eth · 2025-11-11T10:57:27Z

docs/ensnode.io/src/content/docs/docs/usage/api.mdx

+
+**Endpoint:** `GET /api/registrar-actions`
+**Endpoint with custom results count limit:** `GET /api/registrar-actions?limit=5`
+**Endpoint with results sourced for the `eth` parent name:** `GET /api/registrar-actions/eth`


I thought I read code suggesting this filter is implemented by node, not name?

lightwalker-eth · 2025-11-11T11:00:05Z

apps/ensapi/src/handlers/registrar-actions-api.ts

+ *
+ * Responds with:
+ * - 400 error response for bad input, such as:
+ *   - (if provided) `parentName` path param points to a name not associated with any indexed subregistries.


Please see feedback below suggesting this not be an error.

…ction-ens-api

Update HTTP route for Registrar Actions API to use the `parentNode` param instead of the `parentName` one.

Refine response data model by using `NamedRegistrarAction` type.

Introduce `reinterpretName` helper for client-side validation.

lightwalker-eth

@tk-o Hey super updates here 🚀 Shared a few comments and suggestions. Please take the lead to merge when ready 👍

lightwalker-eth · 2025-11-12T22:06:42Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+/**
+ * Reinterpret Label
+ */
+export function reinterpretLabel(label: Label | LabelHash): Label | LabelHash {


This function should only take in Label values and not LabelHash values.

It also should only return InterpretedLabel values and not LabelHash values.

lightwalker-eth · 2025-11-12T22:07:21Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+  // a LabelHash must be encoded
+  if (isLabelHash(label)) return encodeLabelHash(label);


Suggested change

// a LabelHash must be encoded

if (isLabelHash(label)) return encodeLabelHash(label);

This logic should be removed. It is not part of this operation.

lightwalker-eth · 2025-11-12T22:11:03Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+  // no change required for NormalizedLabel
+  if (isNormalizedLabel(label)) return label;
+
+  // otherwise, label cannot be reinterpreted


This needs an update:

The current logic that throws an error here should be removed.

We need to add another check here if the label is an empty string. If it is then this is the only case where this function should throw an error. It violates the invariant that the provided label must never be an empty label.

... now, after all the checks above are completed, we know we have an unnormalized label that is non-empty. For this case we need to do the following:

calculate the labelhash of the (unnormalized) label

build an encoded labelhash from that labelhash (in other words, wrap it in square brackets)

return the encoded labelhash you built

lightwalker-eth · 2025-11-12T22:12:15Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+ * - If label is a {@link LiteralLabel}, then it was mapped into
+ *   {@link EncodedLabelHash}.
+ */
+export type ReinterpretedLabel = Label | EncodedLabelHash;


This type alias can be removed. It doesn't need to exist. The goal of reinterpretLabel is it returns the existing InterpretedLabel type.

lightwalker-eth · 2025-11-12T22:13:01Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+ *
+ * A Name built only from {@link ReinterpretedLabel}s.
+ */
+export type ReinterpretedName = Name;


This type alias can be removed. It doesn't need to exist. The goal of reinterpretName is it returns the existing InterpretedName type.

lightwalker-eth · 2025-11-12T22:38:46Z

packages/ensnode-sdk/src/api/types.ts

+   * - `namehash(name)` is always `action.registrationLifecycle.node`.
   */
-  registrationLifecycle: RegistrationLifecycleWithDomain;
+  name: ReinterpretedName;


Suggested change

name: ReinterpretedName;

name: InterpretedName;

lightwalker-eth · 2025-11-12T22:41:01Z

apps/ensapi/src/handlers/registrar-actions-api.ts

-    value: subregistryNode,
-  };
-}
+const MAX_RESPONSE_ITEMS_COUNT_LIMIT = 1000;


Maybe better to make it only 100?

packages/ensnode-sdk/src/shared/zod-schemas.test.ts

lightwalker-eth · 2025-11-12T22:48:09Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+ *
+ * Allows the ENSNode Client to reinterpret Names returned from ENSApi.
+ */
+export function reinterpretName(name: Name): ReinterpretedName {


Suggested change

export function reinterpretName(name: Name): ReinterpretedName {

export function reinterpretName(name: InterpretedName): InterpretedName {

lightwalker-eth · 2025-11-12T22:59:31Z

packages/ensnode-sdk/src/api/filters.ts

+  /**
+   * Build a "parent node" filter object for Registrar Actions query.
+   */
+  byParentNode(parentNode: Node | undefined): RegistrarActionsFilter | undefined {


Thanks for aligning if this query param was by name or node.

I continue to believe the query param should actually be the AccountId of a subregistry (a subregistryId).

Reasons for this include:

The data model in the database for registrar actions stores an associated subregistryId rather than name or node.

The subregistry for a name (or node) can change across time. For example when ENS made their registry migration the subregistryId for Ethnames changed. Let's imagine this happens again for some reason. This would mean the subregistryId for Ethnames would change again and therefore suddenly all RegistrarActions returned by an API call passing in parent name / node X would suddenly disappear.

Please also have a look at the work Mykola is advancing in PR 1239: feat: introduce ENSAnalytics API into ENSApi #1239 Please note how the API he's working on there builds the in-memory cache of aggregated referrer metrics based on a specific subregistryId, not on a name or node. It would be nice if we align related logic across what both of you guys are working on.

What do you think?

If AccountId is the ID we'd like to use, I'm ok with having it implemented 👍

@lightwalker-eth deeper thinking, my suggestion is to continue using the parent node filter for registrar actions, as it feels like a perfect balance between user experience (namehash of a particular name) and our current data model constraints (unique node values across all subregistries.

Update `reinterpretName` implementation

lightwalker-eth

@tk-o Hey thanks for your updates on this PR. Here's some feedback that would be good to refine in your next PR. Thanks 👍

lightwalker-eth · 2025-11-13T12:07:33Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

-export function reinterpretName(name: Name): ReinterpretedName {
-  if (name === "") return name;
+export function reinterpretName(name: InterpretedName): InterpretedName {
+  if (name === "") return name as InterpretedName;


name is already an InterpretedName, therefore should be no need for "as ..." here.

lightwalker-eth · 2025-11-13T12:10:14Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

-export type ReinterpretedName = Name;
-
 /**
 * Reinterpret Label


We should document here that:

* Reinterprets {@link InterpretedLabel} values received by "External System" * into {@link InterpretedLabel} values in "Internal System" where: * 1. "External System" is not guaranteed to be using the same ENSNormalize * version as "Internal System", and therefore the `InterpretedLabel` passed into * this function (from "External System") is not guaranteed to 100% align * with the invariants of an `InterpretedLabel` in "Internal System". * 2. The `InterpretedLabel` returned by this function is guaranteed to match * the invariants of `InterpretedLabel` in "Internal System".

lightwalker-eth · 2025-11-13T12:10:55Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

 * Reinterpret Label
+ *
+ * @returns reinterpreted label.
+ * @throws an error when the provided label must never be an empty label.


"@throws an error if the provided label is an empty label (and therefore violates the invariants of an InterpretedLabel)."

lightwalker-eth · 2025-11-13T12:11:24Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

-
-  // no change required for EncodedLabelHash
-  if (isEncodedLabelHash(label)) return label;
+export function reinterpretLabel(label: Label): InterpretedLabel {


The param for this function should change from Label to InterpretedLabel.

lightwalker-eth · 2025-11-13T12:11:54Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

-  // no change required for EncodedLabelHash
-  if (isEncodedLabelHash(label)) return label;
+export function reinterpretLabel(label: Label): InterpretedLabel {
+  // Invariant: the provided label must never be an empty label.


"Invariant: InterpretedLabel values must never be an empty label."

lightwalker-eth · 2025-11-13T12:13:14Z

packages/ensnode-sdk/src/shared/reinterpretation.ts


  // no change required for NormalizedLabel
-  if (isNormalizedLabel(label)) return label;
+  if (isNormalizedLabel(label)) return label as InterpretedLabel;


Should be no need for "as InterpretedLabel" here.

lightwalker-eth · 2025-11-13T12:14:33Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

-export function reinterpretName(name: Name): ReinterpretedName {
-  if (name === "") return name;
+export function reinterpretName(name: InterpretedName): InterpretedName {
+  if (name === "") return name as InterpretedName;


I'm not 100% confdent on how the split / join operations work on an empty string input. But possibly we don't need this explicit check for the empty string.

lightwalker-eth · 2025-11-13T12:15:14Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+ * Reinterprets {@link InterpretedName} values received by "External System"
+ * into  {@link InterpretedName} values in "Internal System" where:
+ * 1. "External System" is not guaranteed to be using the same ENSNormalize
+ *    version as "Internal System", and therefore the `Name` passed into


Name in this sentence should change to InterpretedName

I made this typo in my earlier PR feedback.

lightwalker-eth · 2025-11-13T12:16:21Z

packages/ensnode-sdk/src/shared/reinterpretation.ts

+  if (label === "") {
+    throw new Error(`The label must not be an empty string to be reinterpreted.`);
+  }



Ah there's a key issue here! We must keep the check here if the label is an encoded labelhash. If it is, it needs to be returned without changes.

lightwalker-eth · 2025-11-13T12:18:38Z

apps/ensapi/src/lib/middleware/require-registrar-actions-plugins..middleware.ts

- * 3) The omnichain indexing status of the connected ENSIndexer is other than
+ * 2) ENSApi has not yet successfully cached the Indexing Status in memory from
+ *    the connected ENSIndexer.
+ * 3) The omnichain indexing status of the connected ENSIndexer is not


"The omnichain indexing status of the connected ENSIndexer that is cached in memory is not"

Above adds "... that is cached in memory ..."

Co-authored-by: lightwalker.eth <126201998+lightwalker-eth@users.noreply.github.com>

tk-o added 5 commits November 7, 2025 20:14

fix(docs): update plugin references

7435237

feat(ensnode-sdk): serialization logic for price values

f589bd6

fix(ensnode-schema): update registrant field to store hex values

3d512f1

fix(ensnode-schema): introduce RegistrationLifecycleWithDomain type

084f1e5

Also includes related serialization functionality.

feat(ensapi): implement Registrar Actions API

3253060

Introduces a new HTTP route at `GET /api/registrar-actions/latest` which allows fetching the latest "logical registrar actions", including domain information.

vercel bot deployed to Preview – ensnode.io November 7, 2025 19:23 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 7, 2025 19:23 View deployment

Merge remote-tracking branch 'origin/main' into feat/1229-registrar-a…

03e3d3c

…ction-ens-api

vercel bot deployed to Preview – ensrainbow.io November 8, 2025 07:41 View deployment

vercel bot deployed to Preview – ensnode.io November 8, 2025 07:41 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 8, 2025 07:42 View deployment

refactor(ensapi): apply composition to Registrar Actions API

3ff6d0e

Take domain data model away from registrar actions data model. This help keeping types simple, and still enable clients to get data about registration lifecycle domain in an easy way.

vercel bot deployed to Preview – ensrainbow.io November 8, 2025 14:12 View deployment

tk-o mentioned this pull request Nov 8, 2025

feat: Registrar Actions API integration #1242

Closed

3 tasks

vercel bot deployed to Preview – ensnode.io November 8, 2025 14:13 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 8, 2025 14:13 View deployment

lightwalker-eth reviewed Nov 10, 2025

View reviewed changes

tk-o added 2 commits November 10, 2025 14:04

refactor(ensapi): make Domains info part of Registrar Actions API res…

8391d40

…ponse Clients calling the API will have a complete piece of information about each Registrar Action result handy.

vercel bot deployed to Preview – ensrainbow.io November 10, 2025 17:27 View deployment

vercel bot deployed to Preview – ensnode.io November 10, 2025 17:27 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 10, 2025 17:27 View deployment

tk-o added 6 commits November 10, 2025 18:44

docs(registrar-actions-api): create initial docs

0882216

docs(changeset): Update registrant field type on the registrars s…

64664bd

…chema to store hex values.

docs(changeset): Implement Registrar Actions API module.

c2d42fc

docs(changeset): Implement a HTTP endpoint for the Registrar Actions …

6227abd

…API.

docs(changeset): Document the HTTP endpoint for Registrar Actions API.

500bed1

docs(changeset): Implement registrarActions() method on ENSNodeClient.

43af51f

tk-o requested a review from a team as a code owner November 10, 2025 17:52

vercel bot deployed to Preview – ensrainbow.io November 10, 2025 17:53 View deployment

vercel bot deployed to Preview – ensnode.io November 10, 2025 17:53 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 10, 2025 17:53 View deployment

tk-o changed the title ~~WIP feat(ensapi): implement Registrar Actions API~~ feat(ensapi): implement Registrar Actions API Nov 10, 2025

fix: build issue

377cca5

tk-o force-pushed the feat/1229-registrar-action-ens-api branch from a61c673 to 377cca5 Compare November 10, 2025 20:59

vercel bot deployed to Preview – ensrainbow.io November 10, 2025 20:59 View deployment

vercel bot deployed to Preview – ensnode.io November 10, 2025 21:00 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 10, 2025 21:00 View deployment

lightwalker-eth reviewed Nov 11, 2025

View reviewed changes

tk-o added 4 commits November 12, 2025 11:25

Merge remote-tracking branch 'origin/main' into feat/1229-registrar-a…

09beb1f

…ction-ens-api

apply pr feedback

aa47bd1

Update HTTP route for Registrar Actions API to use the `parentNode` param instead of the `parentName` one.

apply pr feedback

24d0ff1

Refine response data model by using `NamedRegistrarAction` type.

apply pr feedback

6f14ab7

Introduce `reinterpretName` helper for client-side validation.

vercel bot deployed to Preview – ensrainbow.io November 12, 2025 14:57 View deployment

vercel bot deployed to Preview – ensnode.io November 12, 2025 14:58 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 12, 2025 14:58 View deployment

lightwalker-eth approved these changes Nov 12, 2025

View reviewed changes

apply pr feedback

3415c85

Update `reinterpretName` implementation

vercel bot deployed to Preview – ensrainbow.io November 13, 2025 09:24 View deployment

vercel bot deployed to Preview – ensnode.io November 13, 2025 09:25 View deployment

vercel bot deployed to Preview – admin.ensnode.io November 13, 2025 09:25 View deployment

tk-o merged commit df1cf8c into main Nov 13, 2025
10 checks passed

tk-o deleted the feat/1229-registrar-action-ens-api branch November 13, 2025 09:25

github-actions bot mentioned this pull request Nov 11, 2025

Release New Version #1180

Merged

tk-o mentioned this pull request Nov 13, 2025

Create HTTP API Route for fetching latest registrations #1229

Closed

lightwalker-eth reviewed Nov 13, 2025

View reviewed changes

tk-o added a commit that referenced this pull request Nov 13, 2025

apply remaining PR #1265 feedback

13a8fd7

tk-o added a commit that referenced this pull request Nov 13, 2025

apply remaining PR #1265 feedback (#1271)

7b78825

Co-authored-by: lightwalker.eth <126201998+lightwalker-eth@users.noreply.github.com>

		registrarActions: RegistrarAction[];
		registrationLifecycleDomains: Record<Node, RegistrationLifecycleDomain>;

	// if errorResponse is could not be determined,
	// if errorResponse could not be determined,

	// build the result referencing the "logical registrar action"
	// build the resulting "logical registrar action"

		Track all "logical registrar actions" performed by users across multiple
		subregistries with the Registrar Actions API. This endpoint returns a list

		// a LabelHash must be encoded
		if (isLabelHash(label)) return encodeLabelHash(label);

	export function reinterpretName(name: Name): ReinterpretedName {
	export function reinterpretName(name: InterpretedName): InterpretedName {

Conversation

tk-o commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Scope

Suggested review order

ENSNode SDK

ENSNode Schema

ENSApi

Uh oh!

changeset-bot bot commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

vercel bot commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lightwalker-eth left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lightwalker-eth left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lightwalker-eth left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tk-o commented Nov 7, 2025 •

edited

Loading

changeset-bot bot commented Nov 7, 2025 •

edited

Loading

vercel bot commented Nov 7, 2025 •

edited

Loading