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

Metadata pages and the log #7

Closed
Scooletz opened this issue Mar 27, 2023 · 0 comments · Fixed by #11
Closed

Metadata pages and the log #7

Scooletz opened this issue Mar 27, 2023 · 0 comments · Fixed by #11
Assignees
@Scooletz
Milestone
Foundations

Comments

@Scooletz
Copy link
Contributor

Metadata pages are responsible for holding:

  1. transaction number (always increasing)
  2. block hash
  3. block number

On a reorg scenario, block hash and block number can go back, but the transaction number will always be increasing. In case of a reorg an additional information about the block should be kept so that it's data are not overwritten.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Scooletz Scooletz

Labels
None yet
Projects
Paprika
Status: Done
Milestone
Foundations
Development

Successfully merging a pull request may close this issue.

Root pages and general db refactor NethermindEth/Paprika
1 participant
@Scooletz