Skip to content
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: use updated range proof API #160

Merged
merged 1 commit into from Jan 4, 2023

Conversation

AaronFeickert
Copy link
Contributor

@AaronFeickert AaronFeickert commented Dec 13, 2022

Uses a new range proof API.

Copy link
Contributor

@stringhandler stringhandler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I generally prefer having two methods with different return types rather than one method that returns useful data sometimes, and sentinel values another, but it's subjective so not too fussed

match RistrettoRangeProof::verify_do_not_recover_masks(self.transcript_label, &[statement], &[
rp.clone()
]) {
match RistrettoRangeProof::verify_batch(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a fan of returning different data based on the action, but I think that's subjective, so think it's fine

@stringhandler stringhandler merged commit be0a491 into tari-project:main Jan 4, 2023
@AaronFeickert AaronFeickert deleted the range-proof-api branch January 4, 2023 15:46
stringhandler pushed a commit to tari-project/tari that referenced this pull request Jan 4, 2023
Description
---
Updates `tari-crypto` dependencies to use range proof batch splitting.

Motivation and Context
---
An [earlier PR](#5049) removed an unnecessary restriction on range proof batch splitting. Recent `bulletproofs-plus` work [updates range proof batching](tari-project/bulletproofs-plus#22) to split large batches for performance reasons, and also updates the verification API for clarity. A [corresponding PR](tari-project/tari-crypto#160) in `tari-crypto` uses this new API, but does not change its own external range proof verification API.

This PR updates `tari-crypto` dependencies to take advantage of this new functionality.

How Has This Been Tested?
---
Existing tests pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants