Skip to content
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

Make MultiProvider API more defensive #394

Closed
yorhodes opened this issue May 5, 2022 · 3 comments · Fixed by #767
Closed

Make MultiProvider API more defensive #394

yorhodes opened this issue May 5, 2022 · 3 comments · Fixed by #767
Assignees
Labels

Comments

@yorhodes
Copy link
Member

yorhodes commented May 5, 2022

Allow users to instantiate with fewer networks than app abstraction
Ensure signer exists when using eth_send
Ensure provider exists when using eth_call

@yorhodes yorhodes mentioned this issue May 5, 2022
@nambrot
Copy link
Contributor

nambrot commented May 6, 2022

MultiProvider should have methods to get the signer #343 (comment)

@yorhodes
Copy link
Member Author

related #462

@nambrot nambrot assigned nambrot and unassigned jmrossy May 31, 2022
@nambrot nambrot assigned jmrossy and unassigned nambrot Jun 17, 2022
@jmrossy
Copy link
Contributor

jmrossy commented Jul 1, 2022

@yorhodes Can you clarify how 462 is related here? I can see the value of ChainConnection being a provider but not so sure how it relates to this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants