Sifis Lagouvardos

Hi, how are you inspecting the decompilation output? With the default settings I'm seeing 4 different signatures and 10 event emissions (`LOGx` instructions) in our decompilation output. I ran this...

I use ubuntu 20.04 and souffle 2.0.2. My best guess would be a corrupted input file. In my case I got the bytecode from [contract-library](https://library.dedaub.com/contracts/Ethereum/85865A86502ffB25a1cb3BBAc809d814FEB614e9/bytecode?line=1)(If you also look at the...

I think you got the creation bytecode (vs the runtime bytecode which is what we normally analyze). I did the same and only got one event signature out (corresponding to...

Will do. Will update you here.

`EventSignatureInContract` works during the initial decompilation stage by finding all the event topic hexadecimal values and matching as many as possible to the known signatures in [EventSignature.facts](https://github.com/nevillegrech/gigahorse-toolchain/blob/master/EventSignature.facts). On the other...

Added the `LOGIndexedArg` relation: https://github.com/nevillegrech/gigahorse-toolchain/blob/2db01eb04d040c2a2e83e051509ddc34b57dc20a/clientlib/tac_instructions.dl#L316 Just a reminder that in order to output its results you need to add ``` .output LOGIndexedArg ``` to the client you run.

You can add the line with ``` .output LOGIndexedArg ``` in the `clients/analytics_client.dl` for example. Just append it at the end of the file or on any empty line that...

Hi, Can you share a smart contract that you try to decompile (by sharing its address) as well as the command you run and all the output of `gigahorse.py` on...

Hi @snf, Thanks for the PR, will check it out and let you know what I think.

Can you point me to the contract you're looking at? I know its a frequently seen code pattern, I just want to be working on a common example.