trojanMcAfee

I've tried also with a minimum example and it works every time like yours. It fails only when running tests on a fork with my whole system deployed, and the...

If the test fails, you're reproducing the issue @sisco0 . The test is designed to pass (`test/arb-tests/ozel-index.js`) without the `console.log()`. I'm not really sure -without any ts knowledge- how to...

Don't know if @sloreti managed to log the response error, but I tried adding a log right below that line, like you're mentioning, @fvictorio , and got no response either....

This is the error btw: ``` const error = new ProviderError("HttpProviderError", -1); ^ ProviderError: The execution failed due to an exception. at HttpProvider.request (xxxxxxx/node_modules/hardhat/src/internal/core/providers/http.ts:49:19)

Got it! Thanks @ggrieco-tob What about the 3rd scenario? That's actually the one that concerns me since I'm using the Diamond pattern which relies heavily on delegatecall.

Another question, in regards to the 1st scenario, how do you suppress that behavior that produces the `BalanceTooLow` error? Because if you're fuzzing with thousands of txs, eventually the amount...

Any feedback on scenario number 3? @ggrieco-tob

I solved it by just approving OneSplitAudit to spend my coins, and it worked with `0x50FDA034C0Ce7a8f7EFDAebDA7Aa7cA21CC1267e`

I think @alexdevassy was running a standalone analysis instead of a python script with its own constraints, so adding more balance wouldn't be possible here. I'm mentioning it because I'm...

I was having the same error (`echidna-test: Error running slither:`) but it worked doing the echidna call like `~/echidna-test/echidna-test contracts/MyContract.sol --config echidna-config.yaml --contract MyContract`. With a `echidna-config.yaml` file with the...