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

Make it clear that the CRangeCheck is not called on explicit values #959

Merged

Conversation

stevenroose
Copy link
Member

That is enforced by the VerifyAmounts method for regular transactions
and by the VerifyIssuanceAmounts method for issuance values.

That is enforced by the `VerifyAmounts` method for regular transactions
and by the `VerifyIssuanceAmounts` method for issuance values.
@stevenroose
Copy link
Member Author

Let's await CI to see if I might have missed something, but I'm pretty confident that that assertion always holds.

Copy link
Member

@sanket1729 sanket1729 left a comment

Choose a reason for hiding this comment

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

tACK a8a1a93.

Verified that all tests pass locally and checked that the only two calls for CRangeCheck are never called on explicit amounts.
Asserting this is safe and helpful.

@gwillen
Copy link
Contributor

gwillen commented Feb 26, 2021

utACK, although I'm not sure how much good review will do here -- if it tests ok, that seems like the real check.

@stevenroose stevenroose merged commit 8c834f7 into ElementsProject:master Mar 2, 2021
apoelstra added a commit to apoelstra/elements that referenced this pull request Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants