Skip to content

Commit

Permalink
Merge #959: Make it clear that the CRangeCheck is not called on expli…
Browse files Browse the repository at this point in the history
…cit values

a8a1a93 Make it clear that the CRangeCheck is not called on explicit values (Steven Roose)

Pull request description:

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

Tree-SHA512: 69064ca21dbe3a574f38ba8ea9a13cc2d4b6d0ac2b306fad59ff6fa92e63e08c8f4607da82c31731dcf91044eb47c8d79ced2ff49c7c0843343f438eb8bac943
  • Loading branch information
stevenroose committed Mar 2, 2021
2 parents 3b8e407 + a8a1a93 commit 8c834f7
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions src/confidential_validation.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,7 @@ CAmountMap GetFeeMap(const CTransaction& tx) {
}

bool CRangeCheck::operator()() {
if (val->IsExplicit()) {
return true;
}
assert(val->IsCommitment());

if (!CachingRangeProofChecker(store).VerifyRangeProof(rangeproof, val->vchCommitment, assetCommitment, scriptPubKey, secp256k1_ctx_verify_amounts)) {
error = SCRIPT_ERR_RANGEPROOF;
Expand Down

0 comments on commit 8c834f7

Please sign in to comment.