-
Notifications
You must be signed in to change notification settings - Fork 219
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
feat!: add domain consensus hashing to all previous uses of default consensus hashing #4522
feat!: add domain consensus hashing to all previous uses of default consensus hashing #4522
Conversation
47d2a19
to
a1e0174
Compare
@@ -364,18 +368,67 @@ pub(crate) mod hash_serializer { | |||
} | |||
} | |||
|
|||
pub(crate) mod fixed_hash_serializer { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strange place for this. Shouldn't this live with FixedHash ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is in the same place as pub(crate) mod hash_serializer
When trying to move:
Module tari_core::blocks::block_header::fixed_hash_serializer
uses module tari_core::blocks::block_header
which will be inaccessible after move
- Added domain hashing to all previous uses of default consensus hashing. - Changed `output_mr`, `witness_mr `kernel_mr` and `input_mr` types in `pub struct BlockHeader` to be `FixedHash` instead of variable length `BlockHash`. - Fixed unit tests. - Fixed cucumber tests.
a1e0174
to
ea53fac
Compare
Description
output_mr
,witness_mr
,kernel_mr
andinput_mr
types inpub struct BlockHeader
to beFixedHash
instead of variable lengthBlockHash
.Motivation and Context
As per issue #4396.
How Has This Been Tested?