-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mempool: Split into more well-defined components #1741
Merged
Merged
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
iljakuklic
requested review from
OBorce,
TheQuantumPhysicist,
ImplOfAnImpl and
azarovh
April 30, 2024 20:54
iljakuklic
force-pushed
the
mempool-split
branch
2 times, most recently
from
April 30, 2024 22:13
1312cba
to
de7d0c9
Compare
TheQuantumPhysicist
approved these changes
May 1, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the comments, looks OK.
iljakuklic
force-pushed
the
mempool-split
branch
2 times, most recently
from
May 1, 2024 14:05
c7190c4
to
fa78af2
Compare
azarovh
approved these changes
May 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't provide any valuable feedback except that it looks reasonable
This is a refactoring of mempool that splits it into multiple better isolated components with more well defined interfaces between them. * Top-level mempool acts as a coordinator and contains the other two as subcomponents. It also manages the emission of events and the contents of the orphan work queue. Upon reception of a transaction, it first attempts it to add to the transaction pool, and if it is rejected, it tries to add it to the orphan pool. If it's rejected by both, the transaction is rejected for good. * Transaction pool is the main mempool component. It holds transactions and keeps track of the utxo set defined by the transactions in the pool. It is also responsible for validating transactions upon insertion. * The orphan pool is a temporary holding space for transaction for which we do not know the complete set of parents. Some other minor changes are also included: * Remove `Arc` from around `MempoolConfig` (not needed) * Move some definitions to more logical places
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.
This is a refactoring of mempool that splits it into multiple better isolated components with more well defined interfaces between them.
Some other minor changes are also included:
Arc
from aroundMempoolConfig
(not needed)