Skip to content

doc: clarify why blinding factor range proof is needed - #3783

Closed
starius wants to merge 1 commit into
mimblewimble:masterfrom
starius:clarify-range-proof-of-blinding-factor
Closed

doc: clarify why blinding factor range proof is needed#3783
starius wants to merge 1 commit into
mimblewimble:masterfrom
starius:clarify-range-proof-of-blinding-factor

Conversation

@starius

@starius starius commented Mar 10, 2024

Copy link
Copy Markdown

This place in the intro was very hard to me to understand. I think now it is easier to understand the logic of why range proofs of blinding factors are needed. Hopefully it helps future readers!

@IRsoctierDT

Copy link
Copy Markdown

True

@Anynomouss Anynomouss left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I agree that the description could be made a bit clearer, but the proposed changes are also confusing. I would suggest to change the text as follows:

This output ((113 + 99)*G + 2*H) requires that both the numbers 113 and 99 are known in order to be spent; the attacker would thus have successfully locked Carol's UTXO. The requirement for a range proof for the blinding factor prevents this because the attacker doesn't know the number 113 and thus neither (113 + 99). In other words, without knowing the private key (blinding factor), the attacker would not know the value in the output and would not be able to produce a valid range proof for it. A more detailed description of range proofs is further detailed in the range proof paper.

@wiesche89

Copy link
Copy Markdown
Contributor

PR #3840 includes @Anynomouss review.

@wiesche89 wiesche89 closed this May 26, 2026
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.

4 participants