Add rpc validation#162
Open
lucasbalieiro wants to merge 4 commits into
Open
Conversation
919857a to
340ee1a
Compare
Collaborator
Author
340ee1a to
a8fb1fc
Compare
This was referenced May 23, 2026
Draft
Member
a8fb1fc to
870bfe4
Compare
Collaborator
Author
Member
|
I just tested again, and on Linux it's not able to get the information through RPC. |
Member
|
To make it work on my Linux, both dev and docker deployments, I had to push this commit: GitGab19@26dd208 You can find it at https://github.com/GitGab19/sv2-ui/tree/pr-162 in case you want to cherry-pick it. |
Collaborator
Author
GitGab19
approved these changes
May 27, 2026
Member
GitGab19
left a comment
There was a problem hiding this comment.
Great, I tested everything and it's working on my end.
This file contains hidden or 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
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.


to be merged after #159
closes #161
This is adding a RPC auto-discovery that will try to probe the network, version and IBD state of the node.
For testing I've listed the edge cases that I found when working on this here: #161 (comment)
Also, I recommend testing from the dev mode and from the docker node.
Some prints of my test cases: