Skip to content
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

Implement EXTCODEHASH opcode for Constantinople #1147

Merged
merged 1 commit into from
Aug 8, 2018

Conversation

cburgdorf
Copy link
Contributor

@cburgdorf cburgdorf commented Aug 6, 2018

What was wrong?

Missing the EXTCODEHASH opcode as specified for Constantinople (#719)

How was it fixed?

Implemented it.

Known issues

  • test_opcodes got more messy as we are reusing one computation setup strategy across all tests. (though, I think it's not that bad yet)
  • some test cases are rather vague to me and I couldn't find geth or parity covering these either

Cute Animal Picture

put a cute animal picture link inside the parentheses

@cburgdorf cburgdorf force-pushed the christoph/feat/extcodehash branch 3 times, most recently from 8258c93 to fcea138 Compare August 7, 2018 14:56
Copy link
Member

@pipermerriam pipermerriam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a link to the EIP in the docstring of the opcode function?

@cburgdorf cburgdorf merged commit 9695e6e into ethereum:master Aug 8, 2018
@@ -56,6 +56,7 @@
GASPRICE = 0x3a
EXTCODESIZE = 0x3b
EXTCODECOPY = 0x3c
EXTCODEHASH = 0x3f
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick

The other opcodes are in byte order, maybe put this after RETURNDATACOPY?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking back and forth for a minute when I wrote it but then settled with alphabetical order as that is the chosen order at most other places (e.g. in mnemonics). But now that I think about it again, would probably have made sense to use byte order here to stay consistent within this location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants