Ziga/fix gateway frontend issues after geth rpc #1857
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
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.
Why this change is needed
After merging PR with Geth RPC there were some frontend issues. But we decided to fix them in this PR.
What changes were made as part of this PR
fixed the response of the
/network-healthendpoint (before this endpoint was not used and request was forwarded to ethereumRPC handler which forwarded the response to the node. After implementing geth RPC we don't have that endpoint and this endpoint was actually called. I decided to return the response in the same format as before).fixed some differences regarding encryptionToken and
0xprefix that emerged in that PR.PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks