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

SyncBlockState hash collision issue #459

Open
damian-orzechowski opened this issue Jan 17, 2025 · 0 comments · May be fixed by #460
Open

SyncBlockState hash collision issue #459

damian-orzechowski opened this issue Jan 17, 2025 · 0 comments · May be fixed by #460
Assignees
@damian-orzechowski

Comments

@damian-orzechowski
Copy link
Contributor

SyncBlockState component internally uses a HashSet to quickly identify proof nodes and store them separately for additional proof processing required by snap sync. This is prone to hash collision issues and can give false results during proof node identification.
@damian-orzechowski damian-orzechowski self-assigned this Jan 17, 2025
@damian-orzechowski damian-orzechowski linked a pull request Jan 17, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@damian-orzechowski damian-orzechowski

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix SyncBlockState hash collision issue NethermindEth/Paprika
1 participant
@damian-orzechowski