Timeline for How can I verify that a contract on the blockchain matches the source code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2017 at 23:34 | comment | added | Thomas Jay Rush | I didn't realize the decompiler used the ABI. That clearly makes it a lot easier. | |
| Aug 10, 2017 at 22:26 | comment | added | emx | Noted. This would indeed make decompilation unpractical for complex contracts. | |
| Aug 10, 2017 at 22:03 | comment | added | Thomas Jay Rush | Not always. I've seen many that don't. | |
| Aug 10, 2017 at 22:02 | comment | added | emx | The Contract ABI contains all the variable names. | |
| Aug 9, 2017 at 20:19 | comment | added | Thomas Jay Rush | I'm fairly confident that this cannot work to any level of efficiency, especially for larger contracts. The names of the variables are not stored in the byte code, so the decompiler must create its own names. Trying to see if the decompiled code is the same as represented source would be very difficult, I would think. | |
| Aug 9, 2017 at 11:57 | review | First posts | |||
| Aug 9, 2017 at 12:35 | |||||
| Aug 9, 2017 at 11:55 | history | answered | emx | CC BY-SA 3.0 |