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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: alloy-dyn-contract #149
feat: alloy-dyn-contract #149
Changes from 8 commits
7b4eee2
5f551bd
a095780
fb4b625
f220ca5
0dac516
55d1988
2d3e5da
89409bf
d383e6f
589a28c
3bcaa00
cd15d2d
daf2ad7
99c2082
25b0d71
1a6b0ca
c87bc9c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think having access to the CallRequest would be ideal. This way we can get around not having
send_transaction
on the provider by transferring the fields manually to a signable/rlp-able tx type from alloy consensus e.gTxLegacy