Revisit 2278: Unify hash digest format on both sides (MIPS + Keccak) #2480
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.
This is based upon #2278.
The only difference is that the above PR assumed that bytes corresponding to the length of the preimage were always read in a different instruction than actual preimage bytes. But I am no longer sure that I had checked that thoroughly back then, so I am creating this PR to solely include the fix for the hash digest format: that is, making sure that both in MIPS and Keccak the data sent to the communication channel corresponds to the 31 bytes of the preimage (no MSB in either of them). I left the check of the length bytes as a FIXME for the future.