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

keep a table of ingested block headers #272

Open
rafaelcr opened this issue Oct 7, 2024 · 0 comments
Open

keep a table of ingested block headers #272

rafaelcr opened this issue Oct 7, 2024 · 0 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@rafaelcr
Copy link
Collaborator

rafaelcr commented Oct 7, 2024

To optimize how we determine if we've already ingested a block, we should keep a blocks table with only header data (block hash and height). This way, if we receive a new chainhook payload we can determine with full certainty if we have already ingested that block before instead of comparing only block heights which may be deceptive and vulnerable to reorgs.

@rafaelcr rafaelcr added the bug Something isn't working label Oct 7, 2024
@rafaelcr rafaelcr self-assigned this Oct 7, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in API Board Oct 7, 2024
@smcclellan smcclellan moved this from 🆕 New to 📋 Backlog in API Board Oct 14, 2024
@smcclellan smcclellan added the good first issue Good for newcomers label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants