-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decompiled version :) #1
Comments
It seems like the decompiled code is missing the constructor setup among other things. Not sure how the decompiler works and I’m less familiar with vyper. Interesting to see if come back in that form however.
I’m using a lot of memory tricks which are probably unothadox to reconstruct from bytecode. I bet that decompiler is use to targeting contracts made with Solidity and probably looks for Solidity like internal opcode patterns to reconstruct what’s there. Because this is written in almost raw assembly those queues won’t be there. Anyway, that might be the reason.
…Sent from my iPhone
On May 10, 2019, at 8:33 PM, Tomasz Kolinko ***@***.***> wrote:
Here's the Eveem-decompiled version of the deployed part, I wonder if it gets it right:
https://eveem.org/code/0x702248ccd521ec17
I got it by pasting this:
361560f65760003681610424376104a8516103e87f4a0a6d86122c7bd7083e83912c312adabf207e986f1ac10a35dfeb610d28d0b68152600180300180546104088181526104c8915085822061046852601987538384537fb0609d81c5f719d8a516ae2f25079b20fb63da3e07590e23fbf0028e6745e5f260025260a0852060225260428720945086875b305481101560d0576104286060820261048851010187815261012c6020816080848e8c610bb8f1508381515411151560c0578a8bfd5b8051935050505b8581019050608a565b505080518401835550858686836104285161044851f4151560ef578586fd5b5050505050505b
Into here:
https://eveem.org/pro/
What I find curious is that one of the asserts in the loop seems missing - I checked the assembly, and it seems that it's not there indeed ( https://eveem.org/asm/0x702248ccd521ec17 ).
I'm probably either doing something wrong here (not really proficient with yul and contract compilation - I do it the opposite way only :) ), or the decompiler doesn't handle this properly? :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's the Eveem-decompiled version of the deployed part, I wonder if it gets it right:
https://eveem.org/code/0x702248ccd521ec17
I got it by pasting this:
361560f65760003681610424376104a8516103e87f4a0a6d86122c7bd7083e83912c312adabf207e986f1ac10a35dfeb610d28d0b68152600180300180546104088181526104c8915085822061046852601987538384537fb0609d81c5f719d8a516ae2f25079b20fb63da3e07590e23fbf0028e6745e5f260025260a0852060225260428720945086875b305481101560d0576104286060820261048851010187815261012c6020816080848e8c610bb8f1508381515411151560c0578a8bfd5b8051935050505b8581019050608a565b505080518401835550858686836104285161044851f4151560ef578586fd5b5050505050505b
Into here:
https://eveem.org/pro/
What I find curious is that one of the asserts in the loop seems missing - I checked the assembly, and it seems that it's not there indeed ( https://eveem.org/asm/0x702248ccd521ec17 ).
I'm probably either doing something wrong here (not really proficient with yul and contract compilation - I do it the opposite way only :) ), or the decompiler doesn't handle this properly? :)
Edit: ah, I can see that's exactly what yul version says it is :) still curious to hear your thoughts
The text was updated successfully, but these errors were encountered: