You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2021. It is now read-only.
It shouldn't be hard to change the underlying local blockchain to a geth instance in dev mode. While ganache has certain features that geth lacks (like time manipulation), there are still some small differences between geth and ganache, and many users will find this useful.
As far as I know, it is not possible to configure geth with a set of private keys, like we do on ganache-core. We should be able however to have those accounts in the provider itself, by adding a step to the setup process where the initial account funds these. This goes in line with the geth team recommending not using the client to store private keys.
The text was updated successfully, but these errors were encountered:
You might want to take this one trufflesuite/truffle#624 into account too, perhaps it becomes an issue during your tests against Geth. I lost several hours of why on earth are my tests not running until I ran into that issue. So I hope I'll save you some time :)
@vicnaum No, but in that case I don't see what benefit there would be to using Test Environment! The main feature is that it will spin up Ganache for you and stop it when your tests end.
Let us know what use case you had in mind so we can consider implementing support for it!
It shouldn't be hard to change the underlying local blockchain to a geth instance in dev mode. While ganache has certain features that geth lacks (like time manipulation), there are still some small differences between geth and ganache, and many users will find this useful.
As far as I know, it is not possible to configure geth with a set of private keys, like we do on ganache-core. We should be able however to have those accounts in the provider itself, by adding a step to the setup process where the initial account funds these. This goes in line with the geth team recommending not using the client to store private keys.
The text was updated successfully, but these errors were encountered: