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

Add known_gaps table #53

Merged
merged 6 commits into from
Mar 31, 2022
Merged

Add known_gaps table #53

merged 6 commits into from
Mar 31, 2022

Conversation

abdulrabbani00
Copy link
Contributor

We will probably need to change the modulus_block_number columns name

We will probably need to change the `modulus_block_number` columns name
@abdulrabbani00 abdulrabbani00 linked an issue Mar 18, 2022 that may be closed by this pull request
@abdulrabbani00 abdulrabbani00 changed the title Add known_gaps table - DO NOT MERGE YET!! Add known_gaps table Mar 30, 2022
@abdulrabbani00 abdulrabbani00 marked this pull request as ready for review March 30, 2022 21:34
Copy link
Collaborator

@i-norden i-norden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Table definition LGTM but we should add the migration as well. I agree we should change that column to modulus_block_number and we should also add another column, something like offset or slot_position. Then we can tell which blocks a specific service is handling no matter how we divide the work up (neglecting the confounding activity of the eth_probes that Rick poined out).

schema.sql Show resolved Hide resolved
@abdulrabbani00
Copy link
Contributor Author

@i-norden - My thought was that based off the processing_number, we would be able to figure out what the offset is. But I would love to understand your thoughts on the extra columns and their value.

@i-norden i-norden merged commit 82f28ae into main Mar 31, 2022
@abdulrabbani00 abdulrabbani00 deleted the feature/known_table branch March 31, 2022 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Known gap table
2 participants