-
Notifications
You must be signed in to change notification settings - Fork 73
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
Move rpc url from config to parameter #51
Comments
Passing around the config variable every time feels a bit clunky. However, enabling the ability to connect to multiple EVMs does seem useful. This is solved by web3.js by simply instantiating multiple web3 instances. The only analog would be to make multiple processes, however that becomes difficult with the statically named processes under the hood. |
Yep spawning new instance of rpc with custom parameters also will work. |
@konstantinzolotarev it's possible
|
@ayrat555 Awesome ! Thank you ! |
It makes more sense to configure RPC client using parameters (not in config)
Otherwise it's impossible to use it as real RPC client.
For example right now it's not possible to connect to 2 different EVMs at same time or reconfigure it without pain.
What do you think about something like this:
The text was updated successfully, but these errors were encountered: