Emilio López

Thanks for the report! Indeed, we're looking to migrate away from pysha3 across several of our tools. The hashlib module does not offer keccak256 hashes (which pysha3 did) so we're...

@rappie if you're able to reproduce it, can you check if running `stty sane` or `tput reset` on the terminal help fix it?

This would allow us to then include the aarch64 binary in eth-security-toolbox.

Action PR is here: https://github.com/haskell-actions/setup/pull/47

Hi @aviggiano, is your `CryticTester` contract on Foundry's `test` or `script` directory by any chance? I believe `crytic-compile` skips building those to improve compilation speeds.

@arcz CI-wise this is good to go, but I think some of the tests are flaky; I had to re-run boolean.sol on 0.8 and harvey_foo.sol on 0.6 for them to...

Hi @aviggiano! Are you targeting standalone `.sol` files or using hardhat/foundry to handle the compilation process (i.e. targeting `.` or a folder)? I see you mention using solc-remaps but I...

Hi! I'll reply inline > Initially, I was running the following command: > > ``` > echidna contracts/TestContracts/invariants/echidna/EchidnaTester.sol --test-mode assertion --contract EchidnaTester --config config.yaml | tee /dev/null > ``` Okay,...

Hi! This error means that deploying the contract code in echidna failed. You can review your code and see how the deployment of VaultFuzzer / VaultContract is failing. Here's some...

The echidna VM (by default at least) has no notion of anything deployed on a real, live chain though. Echidna will deploy your `VaultFuzzer` contract on an "empty" blockchain (and...