Skip to content

Conversation

@shrugs
Copy link
Collaborator

@shrugs shrugs commented Jun 18, 2025

closes #790

  • renamed package from @ensnode/ens-deployments to @ensnode/datasources
  • removed top-level export in favor of util getDatasourceMap and getDatasource
  • added ENSNamespace type and value using POJO to make public API easier to use
  • refactored DatasourceName into POJO enum as well
  • 'ENS deployment' -> 'ENS namespace'
  • all 'deployment' references are now exclusively referring to the concept of a devops deployment of ENSNode
  • original plugin namespace concept renamed to pluginNamespace
  • Deployment -> DatasourceMap

@shrugs shrugs requested a review from a team as a code owner June 18, 2025 18:58
@changeset-bot
Copy link

changeset-bot bot commented Jun 18, 2025

🦋 Changeset detected

Latest commit: dd0de1c

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

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
Copy link

vercel bot commented Jun 18, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
admin.ensnode.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 23, 2025 11:17am
ensnode.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 23, 2025 11:17am
ensrainbow.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 23, 2025 11:17am

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

@shrugs Hey nice updates 👍 Reviewed and shared suggestions. Please merge when ready 🙌

@shrugs
Copy link
Collaborator Author

shrugs commented Jun 20, 2025

once again suggesting the replacement of L1Chain and associated words with ENS namespace and ENSNamespace. the language around using L1Chain is verbose and confusing, and it seems extremely clear to me that what we're discriminating between, at the top-level, is isolated ENS namespaces, not "L1s that host the root registry". as you said yourself there could be another deployment of ENS to mainnet, and ENSNode could technically support it — it's not the L1 that is the unique discriminator, it's the ENS namespace itself (and its associated contract addresses etc) that we're switching between. the ensroot Datasource defines which chain hosts the ENS Root contracts.

i.e. just replacing the word "deployment" with "namespace", no other logical changes.

i don't know, this seems extremely clear to me, but perhaps i'm missing something?

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

@shrugs Hey super updates here 😄 Reviewed and shared a few ideas 👍

@shrugs shrugs changed the title rename ENS_DEPLOYMENT_CHAIN (+etc) to L1_CHAIN (+etc) refactor ens-deployments package (now datasources) & usage Jun 20, 2025
@shrugs
Copy link
Collaborator Author

shrugs commented Jun 21, 2025

i'm in favor of not using the datasource/instance terminology, i don't see the specific need for it

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

@shrugs Very happy. Awesome updates that help to simplify the mental model a lot!

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

A few other little ideas 👍 @shrugs Please decide as you wish.

@shrugs
Copy link
Collaborator Author

shrugs commented Jun 23, 2025

i've gone with the verbose but explicit DatasourceMapFullyDefinedAtCompileTime and associated function names to clearly communicate its behavior

@shrugs
Copy link
Collaborator Author

shrugs commented Jun 23, 2025

and i've refactored the global config usage out of the ponder-helper and plugin-helpers for better separation of concerns

@shrugs shrugs merged commit 4ee9eb7 into main Jun 23, 2025
7 checks passed
@shrugs shrugs deleted the fix/ens-deployment-chain branch June 23, 2025 11:19
@github-actions github-actions bot mentioned this pull request Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename ENS_DEPLOYMENT_CHAIN to ROOT_CHAIN or L1_CHAIN

3 participants