-
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
fix: make monero extra data less strict #6117
fix: make monero extra data less strict #6117
Conversation
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.
Happy for this to go in
@@ -105,8 +105,11 @@ pub fn verify_header( | |||
) -> Result<MoneroPowData, MergeMineError> { | |||
let monero_data = MoneroPowData::from_header(header, consensus)?; | |||
let expected_merge_mining_hash = header.merge_mining_hash(); | |||
let extra_field = ExtraField::try_parse(&monero_data.coinbase_tx_extra) | |||
.map_err(|_| MergeMineError::DeserializeError("Invalid extra field".to_string()))?; | |||
let extra_field = ExtraField::try_parse(&monero_data.coinbase_tx_extra); |
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.
Is there no other data about the error here?
Maybe create an issue to add more data about what went wrong
Test Results (CI)1 269 tests 1 269 ✅ 11m 26s ⏱️ Results for commit c67d4d0. ♻️ This comment has been updated with latest results. |
Description
It reverts a change to make the extra field acceptance less strict.
Motivation and Context
Tari only cares about the Merge mining field and not the rest. As long as that deserializes correct we are secure.