Add WalletDb Initialization to MempoolNode::new() in src/mempool.rs #101
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.
PR Description: Add WalletDb Initialization to MempoolNode
Summary of Changes
This PR implements the initialization of
WalletDbwithin theMempoolNode::new()function located insrc/mempool.rs. The changes mirror the existing wallet initialization setup found insrc/miner.rs, ensuring consistent functionality across the modules.Motivation
The addition of the
WalletDbinitialization to theMempoolNodeis aimed at enhancing the wallet handling capabilities of the mempool by providing access to theWalletDbinstance. This aligns with the overall design goal of improving the integrity and accessibility of wallet data throughout various components of the application.Background
The
WalletDbhas been established in theminer.rsfile to facilitate wallet operations during mining processes. By replicating this setup in themempool.rs, we ensure that wallet functionalities are consistently applied where needed, particularly within the context of transaction management and mempool operations.Testing Instructions
MempoolNodeoperates as expected.WalletDbfunctionalities are correctly integrated and accessible in the mempool context.Known Issues
There are no known issues at this time. However, future thorough testing may uncover edge cases that need to be addressed.
Feel free to reach out with any questions or for further clarification regarding this PR.