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

Allow .connect() to different provider/signer #536

Open
Maurechi opened this issue Apr 9, 2024 · 0 comments
Open

Allow .connect() to different provider/signer #536

Maurechi opened this issue Apr 9, 2024 · 0 comments

Comments

@Maurechi
Copy link

Maurechi commented Apr 9, 2024

Is your feature request related to a problem? Please describe.
I have a setup where I need to know in which chains has a contract been deployed. With the current setup (unless there's some feature that I haven't found) this isn't really possible since hardhat-deploy connects to the chain specified on hardhat bash script

Describe the solution you'd like
Would be good to allow some sort of deployments.connect(provider/signer) function so that deploy plugin can change chains seamlessly.

Describe alternatives you've considered
I've created my own scripts that read from the deployments folder and If I'm iterating over chains, i'm able to pass the provider/chainId of the chain so that It can look over the specified folder. This setup works only for read operations.

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

No branches or pull requests

1 participant