Order by fees when re-adding remaining transactions after persisting block #394
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
erikzhang
approved these changes
Sep 25, 2018
Thacryba
pushed a commit
to simplitech/neo
that referenced
this pull request
Feb 17, 2020
* update dotnet 2.0 * Update setup.md * Update setup.md * update 2.0
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.
After the block is persisted we are re-inserting the transactions back into the message queue; however, since they may not all be processed by the time of the next consensus, they should be added in the order they are meant to be ordered when transactions are added. This makes that happen.