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

feat(l1): verify range #1160

Merged
merged 240 commits into from
Nov 20, 2024
Merged

feat(l1): verify range #1160

merged 240 commits into from
Nov 20, 2024

Conversation

fmoletta
Copy link
Contributor

@fmoletta fmoletta commented Nov 13, 2024

Motivation
When we receive a range of data (be it storage, accounts, nodes) from a snap request response we also receive the edge proofs for the given rate. In order to validate that response and integrate the data received we must verify the proofs in relation to the given range

Description

  • Implement function verify_range which verifies a given range of trie elements with the provided edge proofs and also returns a boolean indicating if there is more state to be fetched after the last key.

Closes None, but it is vital to process the responses from other nodes during snap-sync #184

@fmoletta fmoletta changed the title feat(l1): verify range proof feat(l1): verify range Nov 13, 2024
@fmoletta fmoletta marked this pull request as ready for review November 13, 2024 20:01
@fmoletta fmoletta requested a review from a team as a code owner November 13, 2024 20:01
Copy link
Collaborator

@Arkenan Arkenan left a comment

Choose a reason for hiding this comment

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

LGTM

@Arkenan Arkenan added this pull request to the merge queue Nov 20, 2024
Merged via the queue into main with commit 1c51cbe Nov 20, 2024
13 checks passed
@Arkenan Arkenan deleted the validate-account-range branch November 20, 2024 14:22
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.

3 participants