SEGFAULT
SEGFAULT
I don't think `isContract` is a misnomer anymore than `hasCode` would be. It would be misleading if the function was called `isNotEOA`, but it's not. `hasCode` has the same caveats...
Tagging @odyslam as I know you were the one to add this feature (which is fantastic, by the way, thank you!)
@jrainville I believe I also had to add: `registerModuleGroup("blockchainStackComponents` in `cmd_controller.js` to make this fix work.
still relevant
Echoing that this is still kind of a pain - it's very common to need different solidity compiler versions, sometimes even three different versions, within the same project.
> So now that we have mono-repo support, I guess this could be achieved by adding another settings file with this or read it from somewhere like foundry etc Can...
Got some weird rate limit errors here as well...until I turned down the chunk size. Even though it's well within rate limits, the default chunk size of 1000 didn't work...
Something to check before we merge this: need to make sure that there is now way to game the protocol / exploit something during the upgrade, ie between the first...
> > need to make sure that there is now way to game the protocol / exploit something during the upgrade, ie between the first and second transactions > >...
> > > > need to make sure that there is now way to game the protocol / exploit something during the upgrade, ie between the first and second transactions...