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

Range proof mantissa minimum bit length #1117

Merged

Conversation

christophersanborn
Copy link
Member

Fixes issue #480 - "Choice of range proof params in cli wallet reveals transaction magnitude to very narrow range for Blinded transfers" and provides test case of cli_wallet blind transfers.

…matic) to 49 (the largest bit length that won't exceed GRAPHENE_MAX_SHARE_SUPPLY).
@abitmore abitmore requested a review from pmconrad July 4, 2018 22:01
Copy link
Member

@abitmore abitmore left a comment

Choose a reason for hiding this comment

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

Looks good to me. Best if can wrap the long lines (I'd recommend maximum 130 chars per line).

Copy link
Contributor

@jmjatlanta jmjatlanta left a comment

Choose a reason for hiding this comment

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

All looks good to me as well. Thanks @christophersanborn.

Note: I'm not marking this approved, as I too would like pmconrad to take a look.

@pmconrad pmconrad self-assigned this Jul 17, 2018
@pmconrad pmconrad added 2f Testing Status indicating the solution is being evaluated against the test case(s) 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 4a Low Priority Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists 6 CLI Impact flag identifying the command line interface (CLI) wallet application 6 Security Impact flag identifying system/user security labels Jul 17, 2018
generate_block(app1); head_block++;

// ** Check head block:
BOOST_MESSAGE("Check that all expected blocks have processed");
Copy link
Contributor

Choose a reason for hiding this comment

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

This fails to compile for me (Boost-1.60.0):

tests/cli/main.cpp:474:68: error: ‘BOOST_MESSAGE’ was not declared in this scope
       BOOST_MESSAGE("Check that all expected blocks have processed");

Changing to BOOST_TEST_MESSAGE works.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks! Missed that. (Must have older Boost version.)

Copy link
Contributor

@pmconrad pmconrad left a comment

Choose a reason for hiding this comment

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

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2f Testing Status indicating the solution is being evaluated against the test case(s) 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 4a Low Priority Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists 6 CLI Impact flag identifying the command line interface (CLI) wallet application 6 Security Impact flag identifying system/user security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants