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
When passing a private key with -p to contender setup, make sure the from addresses in the [[setup]] stages and [[create]] stages are funded by the passed key.
If you're using a hard-coded from address, it will not be funded. However, from_pool addresses are funded.
The text was updated successfully, but these errors were encountered:
this issue is not quite as pressing, or even relevant now, since from should now generally be replaced by from_pool. (#72, #65)
Specifying a from address in a setup step implies that the account will always be funded prior to running contender, which is usually not the case, namely when testing any network that isn't a local devnet.
I'd actually like to disincentivise the use of from in general, since from_pool works so well. from addresses in builtin scenarios should be phased out immediately.
We could even remove the existing from functionality entirely, and rename from to act as from_pool (and remove from_pool). There really isn't any need to include hard-coded from addresses in scenario configs, as long as you want them to be portable (used by anyone other than you).
When passing a private key with
-p
tocontender setup
, make sure thefrom
addresses in the [[setup]] stages and [[create]] stages are funded by the passed key.If you're using a hard-coded
from
address, it will not be funded. However,from_pool
addresses are funded.The text was updated successfully, but these errors were encountered: