Skip to content
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.

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

Update ENS Subgraph URL #150

Closed
gskril opened this issue Jun 7, 2024 · 1 comment · Fixed by #151
Closed

Update ENS Subgraph URL #150

gskril opened this issue Jun 7, 2024 · 1 comment · Fixed by #151
Assignees
Labels
type:chore It is not a new feature or bug fix. e.g. update dependencies, change repository configurations

Comments

@gskril
Copy link

gskril commented Jun 7, 2024

The ENS subgraph URL used in this repo (https://api.thegraph.com/subgraphs/name/ensdomains/ens) will have a global rate limit added on June 12. To avoid this, creating your own API key with TheGraph is recommended.

It’s free for the first 100k requests/month, and the ENS DAO Ecosystem Working Group offers potential sponsorships if you go beyond that. Here is a video walking through the setup process (less than 5 mins).

This is due to TheGraph sunsetting its hosted service. The old URL will begin serving requests from an ENS DAO-sponsored API key, so this is not a breaking change for ENS, but it will introduce a more restrictive rate limit.

@gskril gskril added the type:chore It is not a new feature or bug fix. e.g. update dependencies, change repository configurations label Jun 7, 2024
@brunomenezes brunomenezes self-assigned this Jun 10, 2024
@brunomenezes
Copy link
Collaborator

Hi @gskril, thanks for reaching out. I'll have a look at that.

@brunomenezes brunomenezes linked a pull request Jun 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:chore It is not a new feature or bug fix. e.g. update dependencies, change repository configurations
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants