Skip to content
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.

subsquid-quests/ens-subgraph-migration

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 

Repository files navigation

Subsquid Logo

docs.rs Discord

Website | Docs | Discord

ENS Subgraph migration

ATT: We updated and re-opened this quest to submissions on Oct 27th

This quest is to migrate the ENS Subgraph to Squid SDK. The repo for the subgraph can be found here. The resulting squid should match the GraphQL API of the subgraph as close as possible, by migrating schema.graphql. The judges reserve the right to request improvements afther the initial review of the submission. Reach out to the Discord Channel for any tech questions regarding this quest.

Quest Info

Category Skill Level Time required (hours) Max Participants Reward Status
Squid Deployment $\textcolor{orange}{\textsf{Medium}}$ ~100 5 $\textcolor{red}{\textsf{5000tSQD}}$ ended

Acceptance critera

Ultimately, the solutions are accepted at the discretion of judges following a manual review. This sections is a rough guide that is in no way binding on our side.

Some of the reasons why the solution will not be accepted include:

  • squid does not start
  • squid fails to sync fully due to internal errors
  • batch handler filters are not set up correctly (leads to a late sync failure in RPC-ingesting squids)
  • data returned for any query is not consistent with subgraph data

You may find this tool to be useful for squid to subgraph API comparisons.

It is desirable that your solution:

  • includes a suite of test GraphQL queries that touches every schema entity and, if used, every custom resolver at least once, with corresponding subgraph queries (listing in README is enough)
  • has high code quality (readability, simplicity, comments where necessary)
  • uses batch processing consistently
  • avoids any "sleeping bugs": logic errors that accidentally happen to not break the data
  • follows the standard squid startup procedure:
    git clone <repo_url>
    cd <repo_url>
    npm ci
    sqd up
    sqd process &
    sqd serve
    
    If it does not, describe your startup procedure in the README.

Please test your solutions before submitting. We do allow some corrections, but judges' time is not limitless.

To submit, invite the following github accounts to your private repo : @dariaag, @belopash, @abernatskiy and @dzhelezov.

Rewards

tSQD rewards will be delivered via the quests page of Subsquid Cloud. Make sure you use the same GitHub handle to make a submission and when linking to that page.

Winners will be listed at the quest repository README. If you do not wish to be listed please tell us that in an issue in your submission repo.

Useful links

About

A quest to migrate ENS subgraph to Subsquid

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •