Error when running Securify on bytecode hex file about securify HOT 8 CLOSED

Yes I can reproduce it with 0.4.18 and --optimize, progress is tracked in #26.

from securify.

How did you get this bytecode? Which solc version?

Securify appears to run fine with -fs c.sol using the Solidity code in https://etherscan.io/address/0x73Dac1423d69651a6F85462B45260f7c05de3548#code. It also doesn't fail with the corresponding bytecode.

from securify.

I'm not using the solidity source code.
I'm running it on the contract bytecode available on etherchain here - https://www.etherchain.org/account/73Dac1423d69651a6F85462B45260f7c05de3548#code
Somehow the bytecodes on etherchain and etherscan seem to be different. Any reason why?

from securify.

No I don't know anything about etherchain to be honest.

from securify.

Hey @bishwascg

for verified contracts, Etherscan shows the constructor code (i.e. it says Contract Creation Code). Etherchain, however, shows the actual contract code. Therefore, the Etherchain is the right one to use for securify and should work.

We are currently investigating a similar error and will also check out this one.

Thanks for your report.

from securify.

@hiqua According to Etherscan it was compiled with v0.4.18+commit.9cf6e910 with optimization enabled. (https://etherscan.io/address/0x73Dac1423d69651a6F85462B45260f7c05de3548#code)

from securify.

Seemingly solved in #81.

from securify.

Please let us know if this still doesn't work with the last commit on master!

from securify.