EVM/Kernel: use blueprint storage instead of queue

Antonio Locasciorequested to merge
alocascio@evm-remove-queue into master

Context

In a previous MR !11023 (merged), we introduced a blueprint store that is populated by the stage one. This will hold both sequencer blueprints when in sequencer mode and an "inbox blueprint" when in proxy mode. In proxy mode, this means that the storage serves as a fallback inbox.

This MR uses the blueprint storage, getting rid of the queue of proposals. This queue was serving two purposes:

  1. Collecting blueprints to be applied in the stage two: this is now take care of by the blueprint storage
  2. Collecting a kernel upgrade and reading the block in progress in case of a reboot: this is now moved to a new RebootContext struct.

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