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

Tool to verify similarity of FS and Trie #8398

Closed
exalate-issue-sync bot opened this issue Jan 19, 2023 · 3 comments
Closed

Tool to verify similarity of FS and Trie #8398

exalate-issue-sync bot opened this issue Jan 19, 2023 · 3 comments
Assignees

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jan 19, 2023

After FS is created, it is nice to have tool to verify that it has the same data as Trie.

We can compute state root based on FS. Likely it will be quickly enough.

We can consider RocksDB snapshot feature which allows to access data on top of some block. Maybe even col.iter() works.

@Longarithm
Copy link
Member

Some ideas:

  • verify only state of account - if we observed FS data corruption, it may be easier to check each modified account in state
  • current impl will work with offline dump and we can add a trigger to check similarity, say, each day. Here we also need to rely on col.iter() fixing contents of flat storage

@Longarithm Longarithm mentioned this issue Feb 3, 2023
26 tasks
@Longarithm
Copy link
Member

Marcin' work on this in the scope of fast state sync idea: #8531
We can iterate over trie and flat storage simultaneously and check each single key, though state root computation by flat storage would be faster.

@Longarithm
Copy link
Member

Done in #8531

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

No branches or pull requests

1 participant