Revert changes in HashTreeRoot and SSZ encoding for backwards-compatibility #362
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.
Description
fastssz
was upgraded in #324 and it changed the roots forConsensusData
,SignedMessage
andSSVMessage
, which would be a fork.This
fastssz
upgrade included a crucial hashing fix, replacingPutBytes
withAppend
in order to prevent double-merkleization inHashTreeRoot
methods, thereby changing roots for[]byte
fields exceeding 32 bytes.It's noted that Beacon spec tests appear unaffected by this change, as they don't contain fields exceeding the threshold for the double-merkleization bug. However, we don't know that Beacon messages are absolutely not impacted.
The changes that were done to preserve backwards-compatibility:
types.Contribution
was copied over fromv0.3.4
spec.DataVersion
is now being decremented in encodings and incremented in decodings, because all of the values were incremented by 1 in go-eth2-client.