[go: up one dir, main page]

rollup/node: check snapshot import without unsafe patch for origination level

Sylvain R.requested to merge
sribaroud@rollup@snapshot_import_uses_state_without_unsafe_apply_for_genesis_check into master

What

Fixes the import of snapshot for rollup node when there is unsafe patches for the imported snapshot and it's an archive snapshot.

Why

When importing a snapshot for a rollup with some unsafe patch the rollup node fails because it tries to check the modified pvm state hash at the origination level with the genesis commitment.

How

when importing a snapshot, checking state hash at the origination level uses the original pvm state and not the modified one.

Manually testing the MR

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR

Merge request reports