expanded rpc api to add MempoolSizeChanged
#663
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.
Confirmed working with the below wrpc example subscriber:
https://github.com/kaspanet/rusty-kaspa/blob/master/rpc/wrpc/examples/subscriber/src/main.rs
self.client().rpc_api().start_notify(listener_id, Scope::MempoolSizeChanged(MempoolSizeChangedScope {})).await?;
Currently in the kaspa socket server we periodically update mempool size using
getInfoRequest
. With the rusty-socket-server we can now use wRPC notifications to get mempool size updates directly and efficiently, replacing the fullGetInfoResponseMessage
with a more lightweight, real-time mempool size notification.