Joao F. Ferreira

Interesting point, @gsalzer! I am not sure if using the command `nice` would work; this would probably require code changes. See, for example: - https://stackoverflow.com/questions/59579859/set-niceness-of-each-process-in-a-multiprocessing-pool - https://stackoverflow.com/questions/42103367/limit-total-cpu-usage-in-python-multiprocessing

First version in commit a706bab44d91584934f367336f2e8032bdb992fb (I forgot to refer to this issue in the commit). Still TODO: SARIF support (if relevant)

tHANKS, @gsalzer. The version of the mythril tool in the `bytecode` branch was updated and since it might detect more types of vulnerabilities, the sarif mapping will need to be...

@tintinweb I wonder if someone from the team had the chance to look at this? Thanks!

Smartbugs 2.0 fixes this. @gsalzer

Hi! What's the status of this proposal?

Thanks for opening this issue, @SunBeomSo. It's a good point. We have included them as three separate contracts because we tried to be faithful to what we found in our...

Thanks, @nveloso! I would say that the contracts should still be in the dataset, since this is a dataset of _Solidity smart contracts_ and they might be compiled with versions...

I'm tagging @ruimaranhao and @pedrocrvz for their opinion on this.

I suggest the following: 1. We keep these contracts as they are 2. If possible, we add _new_ versions of these contracts where the deadcode is always used I added...