Yannis Sachinoglou

Thank you very much for the information. Would it be possible to point any specific rules in our implementation that could be benefited by the tuning?

Hello, Currently, Securify does not support the import statement. Thank you for pointing that out. I have updated the README so that this is explicit. Just for future reference, the...

Hi Kurt, Unfortunately, Solidity version 0.7.+ is not yet fully supported. We are aware of the issue and we are working on it.

Hello, Unfortunately, I wasn't able to reproduce the error. What result do you get when you run: `docker build -t securify .` then `docker run -it securify -b ` and...

Unfortunately, I haven't been able to reproduce your error. It seems like securify is looking for the datalog file in the wrong place. Could you provide more information on the...

It seems like the problem is related to the souffle binary. Have you tried souffle 1.6.2 instead after following my instructions?

It is probably related to MacOS as you mentioned. I would recommend you to try to compile it in a virtual machine with ubuntu 18.04 or use Docker instead.

Hi Lukas, Securify2.0 analyzes all contracts. However, you can choose to get only the results for the contracts you are interested in by using the argument `--include-contracts`. Yannis

It seems like a bug in the compiler which is caused by the new line character in line 737 of 0x7_solidity.txt ``` "\x19Ethereum Signed Message:\n32" ``` I will try to...

This was caused by the usage of staticcall. I pushed a fix to the develop branch.