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

Superchain traces quality assurance checks #1385

Open
ryscheng opened this issue May 8, 2024 · 1 comment
Open

Superchain traces quality assurance checks #1385

ryscheng opened this issue May 8, 2024 · 1 comment
Assignees
Milestone

Comments

@ryscheng
Copy link
Member

ryscheng commented May 8, 2024

What is it?

We should have some simple strategies to make sure that we're not missing data in our blocks/transactions/traces datasets.

FWIW, FYI
The Goldsky folks do some pretty compute heavy QA, including recomputing merkle trees and whatnot to make sure they don't miss anything. They said they have some lighter-weight scripts they could share regarding comparing block headers.

@ryscheng ryscheng added this to the (c) Op RF4 milestone May 8, 2024
@ryscheng
Copy link
Member Author

ryscheng commented May 8, 2024

would you be doing this in bigquery/outside of the file layer? if so, the easiest one is to check distinct block number counts and min/max block numbers for blocks and any other dataset - the other thing you can do is look at - another thing to do is to check the transaction count in blocks and compare that to the number of transactions with that block hash

for traces, maybe compare distinct transaction hashes between traces and transactions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants