forked from FuelLabs/fuel-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Making relayer independent from the executor (FuelLabs#1625)
It is preparation for the FuelLabs#1568. The changes make relayer storage independent from the executor storage. Before, the relayer and executor shared write ownership to the `Messages` table. The relayer was inserting new messages, and the executor was removing them. With this change, only the executor modifies the `Messages` table(inserts and removes messages). The relayer has its own new `History` table, that stores all events from the DA layer per each height. This change also makes the insertion of upcoming events from DA as part of the state transition, allowing in the future handle [force transaction inclusion](FuelLabs#1626). The change: - Adds blanket implementation for the `VmStorageRequirements` since the executor requires access to the `FuelBlocks` table, and we can inherit this implementation. - Adds new tests for the executor that verifies fetching data from the relayer. - Introduces a new general `Event` type for messages and forced transactions (in the future).
- Loading branch information
Showing
25 changed files
with
822 additions
and
335 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.