Skip to content
This repository was archived by the owner on Aug 5, 2026. It is now read-only.
This repository was archived by the owner on Aug 5, 2026. It is now read-only.

Narrative Overhaul: @ensnode/sdk refactor and dependency inversion #1950

Description

@shrugs

Broken out from #1793.

Scope

  1. Rename @ensnode/ensnode-sdk@ensnode/sdk
  2. Invert dependency: @ensnode/sdk depends on enssdk (not the other way around) for shared types
  3. Consolidate @ensnode/ensrainbow-sdk as a subpath export of @ensnode/sdk
  4. Consolidate @ensnode/ensdb-sdk as a subpath export of @ensnode/sdk
  5. Establish @ensnode/sdk/internal subpath for implementation details shared between ENSNode services

From #1793:

@ensnode/sdk — operator-focused ENSNode-specific exports

  • depends on enssdk for shared types
  • @ensnode/sdk/internal — internal-only shared types/libs between ENSNode services

Context — Omnigraph API evolution

In the short term, APIs like Registrar Actions and Tokenscope may be surfaced within the Omnigraph directly (the current ENSv2 plugin already slightly overlaps with these). In the long term, the Omnigraph may encompass all ENSNode APIs, potentially offering 100% feature parity between a GraphQL surface and an equivalent HTTP/JSON surface. We're not close enough to propose specifics on the unified API yet, but the subpath structure of enssdk is designed to accommodate this evolution.

Breaking changes are acceptable — no transition period required.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    devopsDevOps related

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions