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
And then, if I deploy a contract or try to send a TX, if I have an account added, it will broadcast the transaction instead of running it on the pyevm.
This should be disabled, you should not be able to send transactions on a real network when the API makes you think you are on a forked network.
The text was updated successfully, but these errors were encountered:
charles-cooper
changed the title
boa.env.fork is allowed but will broadcast transactionsboa.env.fork is allowed on NetowrkEnv but will broadcast transactions
Oct 1, 2024
charles-cooper
changed the title
boa.env.fork is allowed on NetowrkEnv but will broadcast transactionsboa.env.fork is allowed on NetworkEnv but will broadcast transactions
Oct 1, 2024
yea, it probably makes sense to raise an exception here for NetworkEnv.
also it looks like you are running with deprecated=False, which tells titanoboa you know what you are doing :). normally at least a warning would be issued.
I can run:
And then, if I deploy a contract or try to send a TX, if I have an account added, it will broadcast the transaction instead of running it on the
pyevm
.This should be disabled, you should not be able to send transactions on a real network when the API makes you think you are on a forked network.
The text was updated successfully, but these errors were encountered: