Updated the pocket-provider to align with more recent updates #2980
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.
While the original pocket provider provided some really great work-arounds to how the Pocket Portal handled it's RPC service, a lot of those unique quirks have since changed, and pocket now provides a more consistent experience.
The big changes to how the Pocket Portal manages it's RPC are as follows:
Since the last update, Pocket Network now supports the following
ethers.js
supported networks:As well as now supporting the following other likely future compatible networks:
These will always be tracked live here.
Additionally, Pocket Network provides public community RPC resources available for the following supported chains:
As well as the following unsupported chains:
All of which will be available here
I'm not sure if these above links constitute a community resource by the ethers definition, but unfortunately, the current means of identifying them is rather hodge-podge at the moment. I've currently left the
isCommunityResource()
method as false, but am happy to go back and figure out the logic for determining that if the above public RPCs do qualify as a community resource.