feat(common): resolve eth_call via RPC provider#2016
Merged
shiyasmohd merged 3 commits intomainfrom Mar 25, 2026
Merged
Conversation
Contributor
Author
|
Note: The large number of files is updating imports/tests/docs. |
LNSD
requested changes
Mar 24, 2026
Contributor
LNSD
left a comment
LNSD
left a comment
There was a problem hiding this comment.
Please, check my comments 🙂
shiyasmohd
force-pushed
the
shiyasmohd/provider-ethcall
branch
3 times, most recently
from
0188277 to
3e0961c
Compare
shiyasmohd
force-pushed
the
shiyasmohd/provider-ethcall
branch
from
3e0961c to
f08dc7f
Compare
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
2 participants
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.
rpc.<network>.eth_call()syntax to calleth_calldirectly via a configured RPC provider"dataset_ref".eth_call()path