-
Notifications
You must be signed in to change notification settings - Fork 804
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
Update the networkState RPC with the latest networking change #555
Comments
Wasn't the idea to deprecate this RPC endpoint? Or was this a different one? |
Yeah, rename it: #558 Gav mentioned that he was looking at it from time to time, and it might indeed not be a bad idea to leave an RPC query for people to look at what their node is doing (as long as we're pretty clear on the fact that what is returned is unstable). |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue still relevant and important. |
Signed-off-by: koushiro <koushiro.cqx@gmail.com>
First of all, we can now have multiple active connections to the same node, so the RPC query should be updated to show multiple addresses when that happens.
Additionally, we should also add a lot of things to this query: the list of notification streams open, the ongoing requests, and so on.
Tackling this issue consists in figuring out exactly what can be added, knowing that the point of this query is to show to humans what the current networking state is.
The text was updated successfully, but these errors were encountered: