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

Rename SHA3 opcode to KECCAK256 #5929

Merged
merged 3 commits into from
Jul 14, 2023
Merged

Conversation

Demuirgos
Copy link
Contributor

Fixes Closes Resolves #

Please choose one of the keywords above to refer to the issue this PR solves followed by the issue number (e.g. Fixes #000). If no issue number, remove the line. Also, remove everything marked optional that is not applicable. Remove this note after reading.

Changes

  • Align with other clients with regards to opcode 0x20 naming : SHA3 -> KECCAK256

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (a change that causes existing functionality not to work as expected)
  • Optimization
  • Refactoring
  • Documentation update
  • Build-related changes
  • Other: Description

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

Notes on testing

Optional. Remove if not applicable.

Documentation

Requires documentation update

  • Yes
  • No

If yes, link the PR to the docs update or the issue with the details labeled docs. Remove if not applicable.

Requires explanation in Release Notes

  • Yes
  • No

If yes, fill in the details here. Remove if not applicable.

Remarks

Optional. Remove if not applicable.

Copy link
Contributor

@smartprogrammer93 smartprogrammer93 left a comment

Choose a reason for hiding this comment

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

As discussed this reflects the execution spec and how other clients name the opcode

@Demuirgos Demuirgos requested a review from rubo July 13, 2023 15:59
@Demuirgos Demuirgos marked this pull request as draft July 13, 2023 17:45
@Demuirgos Demuirgos marked this pull request as ready for review July 13, 2023 17:50
@LukaszRozmej
Copy link
Member

Not sure but the reason for the naming might have been compatibility with Parity/OpenEthereum. maybe this will break something in traces from trace module?

@rubo
Copy link
Contributor

rubo commented Jul 13, 2023

maybe this will break something in traces from trace module?

@LukaszRozmej If any old-style tracing compatibility is broken, then it should be addressed in that particular tracer itself. This should've been renamed long ago, the choice of SHA3 was just historical and not for compatibility reasons. This has already been discussed a year ago.

@rubo
Copy link
Contributor

rubo commented Jul 13, 2023

@Demuirgos Update_known_chain_sizes test fails for Goerli. Not sure what's wrong there.

@benaadams
Copy link
Member

@Demuirgos Update_known_chain_sizes test fails for Goerli. Not sure what's wrong there.

The date has increased; all tests will now fail

@Demuirgos Demuirgos requested a review from rubo July 14, 2023 10:44
@MarekM25 MarekM25 self-requested a review July 14, 2023 11:21
@rubo rubo merged commit 4670b4b into master Jul 14, 2023
61 checks passed
@rubo rubo deleted the Refactor/Rename-Sha3-opcode-to-Keccak256 branch July 14, 2023 11:28
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.

None yet

6 participants