Introduce BFTStore and TransmissionStore
#2123
Draft
Conversation
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
Signed-off-by: Howard Wu <9260812+howardwu@users.noreply.github.com>
howardwu
changed the title
TransmissionStoreBFTStore and TransmissionStore
…narkVM into feat/transmission-store
…t/transmission-store
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This PR implements a
TransmissionStoreto store a list of transmissions based on the current round. This will help replace the in-memory tracking of the transmissions, which could lead to BFT issues when nodes reboot. These transmissions can be GC'd later to reduce state bloat.Note: This will break current the database structure, and we may need to move the
MapIDordering for theTransmissionMapenum.TODO:
LedgerorConsensusStore