careful replacement of SHA3 with KECCAK #152
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial step for ethereum/EIPs#59
|
happy to merge this, but i think it needs to happen only following an EIP ratifying the alteration in nomenclature. |
|
Solidity now has an alias named |
|
Shouldn't it be named |
|
I don't mind either way. What would you prefer @gavofyork ? |
|
i think "KECCAK" is fine as long as it's stated as the 256-bit variant somewhere at the beginning. (technically we used SHA3-256, but we always drop the "-256" suffix) |
gavofyork
approved these changes
Feb 28, 2017
|
@ethers needs resolving |
|
this seems to have made it into |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial step for ethereum/EIPs#59