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

Create staging models for trace data by network #1193

Closed
5 of 8 tasks
ccerv1 opened this issue Apr 7, 2024 · 4 comments
Closed
5 of 8 tasks

Create staging models for trace data by network #1193

ccerv1 opened this issue Apr 7, 2024 · 4 comments
Assignees
Labels
c:data Gathering data (e.g. indexing)

Comments

@ccerv1
Copy link
Member

ccerv1 commented Apr 7, 2024

What is it?

The goal is to have a staging model for each blockchain source that feeds are event data models. This should probably be broken up into smaller issues based on where the data will be coming from (Goldsky vs BigQuery vs ???).

Anyway, here are the trace datasets we want to be able to query, roughly in order of priority:

Tier 1: most important for defining initial impact metrics

  • OP Mainnet
  • Base

Tier 2: large chains that we intend support

  • Ethereum
  • Arbitrum

Tier 3: smaller OP chains required for RF4

  • Zora
  • Frax
  • Mode
  • Metal (tbd - not currently on GoldSky)
@ccerv1 ccerv1 added the c:data Gathering data (e.g. indexing) label Apr 7, 2024
@ccerv1 ccerv1 added this to the Data: Blockchain Traces milestone Apr 7, 2024
@ccerv1 ccerv1 changed the title Create staging models for trace data Create staging models for trace data by network Apr 17, 2024
@ryscheng
Copy link
Member

ryscheng commented May 7, 2024

We probably want to make one for each network, subfiltering on the traces that are "relevant"

This would include anything in oss-directory, maybe other data sources (e.g. like users)

@ryscheng
Copy link
Member

ryscheng commented May 7, 2024

We also need to hook up the traces staging model to int_events

@ravenac95
Copy link
Member

I'm going to move Arbitrum and Metal to separate issues as we just got the metal data and we don't yet have traces for arbitrum.

@ccerv1
Copy link
Member Author

ccerv1 commented May 10, 2024

Closing this out per discussion. Have opened separate issues for the remaining chains included in this issue.

@ccerv1 ccerv1 closed this as completed May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:data Gathering data (e.g. indexing)
Projects
Status: Done
Development

No branches or pull requests

3 participants