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

Atomic Block Production #231

Open
rpanic opened this issue Nov 22, 2024 · 0 comments
Open

Atomic Block Production #231

rpanic opened this issue Nov 22, 2024 · 0 comments
Assignees

Comments

@rpanic
Copy link
Member

rpanic commented Nov 22, 2024

Currently, block production isn't atomic and consistent when it comes to DB writes. If the block production fails in the middle of production or between production and result generation, inconsistent states can occur.
To fix this, two things should be implemented:

  • Make result generation a seperate step in the production pipeline and enable it resume operation in case the sequencer crashed after production and before result generation
  • Create a DB transaction pattern that allows us to encapsulate all of the DB writes done during block production in a single transaction
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

No branches or pull requests

1 participant