-
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: enable revealed-value proofs #5983
feat: enable revealed-value proofs #5983
Conversation
Enabled revealed-value proofs for all output types, which are be controlled via the consensus constants. Range proof types are mapped to output types.
Test Results (Integration tests) 2 files + 2 11 suites +11 55m 15s ⏱️ + 55m 15s For more details on these failures, see this check. Results for commit ee25d1e. ± Comparison against base commit 89b19f6. ♻️ This comment has been updated with latest results. |
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 looks good, I think we just need to make the defaults revealed value so we can test them
Description
Enabled revealed-value proofs for all output types, which are be controlled via the consensus constants. Range-proof types are mapped to output types.
From the merge mining proxy/miner log, coinbase output showing
range_proof_type: RevealedValue
andProof: None
:Note: The faucets changed due to
RangeProofType
now being parsed with snake case -"range_proof_type":"RevealedValue"
changed to"range_proof_type":"revealed_value"
on every output line.Motivation and Context
See #5968
How Has This Been Tested?
Added unit tests
Unit tests pass
Cucumber tests pass
System-level tests
[TO BE COMPLETED]What process can a PR reviewer use to test or verify this change?
Code walkthrough
Review the additional unit tests
Run system-level tests
Breaking Changes