txscript: Rename OP_SHA256 to OP_BLAKE256. #840
Merged
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
jrick
approved these changes
Sep 8, 2017
dajohi
approved these changes
Sep 8, 2017
Decred updated the semantics of this opcode to use blake256, but did not rename the opcode to reflect that. This renames the opcode so that it is clear that a blake256 hash is produced instead of a sha256 hash.
davecgh
force-pushed
the
txscript_rename_sha256_to_blake256
branch
from
c22ba4f to
7c3ff82
Compare
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.
Decred updated the semantics of this opcode to use blake256, but did not rename the opcode to reflect that. This renames the opcode so that it is clear that a blake256 hash is produced instead of a sha256
hash.