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.

Sign up for GitHub

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

Jump to bottom

Handling for static/historic datasets #71

Open
3 of 4 tasks
DistributedDoge opened this issue Mar 7, 2024 · 0 comments
Open
3 of 4 tasks

Handling for static/historic datasets #71

DistributedDoge opened this issue Mar 7, 2024 · 0 comments

Comments

@DistributedDoge
Copy link
Collaborator

Working on this one as we speak.

Some resources we want to grab:

  • have contents that stay the same
  • are hosted in strange places (e.g. Google Sheets, Notion, Github data folder)

We can pin those files on IPFS to simplify fetching logic and ensure they don't break in the future:

  • create IPFS_Resource configured with gateway.
  • create new module assets/static.py with assets representing archival datasets
  • create example assets using this strategy
  • actually submit the PR

Examples of historic datasets:

  • Carl's RPGF3 data OSO-snapshot
  • cGrants (old Gitcoin data from Umar) (see also: OSO-funding)
  • Octant Epoch 0 (Only epoch to use snapshot for allocation)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DistributedDoge