Skip to content

Persist genesis state after genesis loader #9535

@asdacap

Description

@asdacap

Is your feature request related to a problem? Please describe.

  • State is lazily persisted. On clean shutdown, this is fine. On unclean shutdown the expected behaviour is to restart from the last persisted state.
  • Unfortunately, genesis is a bit special. When unclean shutdown happen before any state is persisted it cannot replay from genesis as the genesis was marked as processed which causes genesis loader to not get triggered.
  • In addition to that, genesis processing is not integrated into the standard block processor pipeline, meaning it cant be replayed anyway.

Describe the solution you'd like

  • Force persist or flush of the state right after genesis loader or within genesis loader.

Describe alternatives you've considered

  • Do not load genesis in blocktree if best persisted state is not available. Probably will work also, but not sure what else could break.

Additional context

  • Surge rollup test

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions