This repository was archived by the owner on Apr 4, 2022. It is now read-only.
685/xdai rpc endpoint #692
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
|
anxolin
approved these changes
Sep 28, 2021
anxolin
pushed a commit
that referenced
this pull request
Sep 28, 2021
* Attempting alternative xdai WSS endpoint * Temporarily using Cloudflare's https endpoint for xDai Co-authored-by: Leandro Boscariol <[email protected]>
|
LGTM in develop env-t. |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Part of #685
Quick fix using HTTPS Cloudflare's xDai endpoint instead of default WSS one
To Test
/xdai/address/0x5B0ABE214aB7875562ADeE331dEfF0Fe1912FE42Background
Right now, we have reports that there's no data for xDai. It seems that
wss://rpc.xdaichain.com/wssis the culprit.A more resilient solution is being worked on by @henrypalacios