Added option to use MulticallProvider instead of StaticJsonRpcProvider when using custom provider #148
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
This will use MulticallProvider from 0xsequence/multicall instead of BaseProvider or FallbackProvider
|
The use case is pretty niche, but if you always call multiple methods and/or multiple contracts, this can significantly reduce the time needed to complete the requests. |
Amazing PR. thank you so much @0x67. I will take a look this week. |
0xslipk
added
documentation
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
No option to make aggregated/batched requests.
Issue Number: N/A
What is the new behavior?
Added
batched: booleantoProviderOptionsto create MulticallProvider, this should work on any ethers.js v5 providers.Does this PR introduce a breaking change?
Other information
Not sure if this is relevant, but this is my first ever contribution ever to OSS project, so don't hesitate to correct me.