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 Blind Messages Proof #134

Open
alessandroguggino opened this issue May 11, 2022 · 1 comment
Open

Fix Blind Messages Proof #134

alessandroguggino opened this issue May 11, 2022 · 1 comment

Comments

@alessandroguggino
Copy link
Contributor

I found something new from the Blind signature extension. I know that you are now focused on the core draft but I leave it here :)

In BlindMessagesProofGen:

6. c = HASH(commitment || U\~ || nonce)

In BlindMessagesProofVerify:
4. c\_v = HASH(U || U^ || nonce)

The values in c and cv are inconsistent: we should decide which one to follow.

  1. c = hash(U || U~ || nonce) and cv = hash(U || U^ || nonce) + add U (known messages) as input parameter in BlindMessagesProofVerify
    or
  2. c = hash(commitment || U~ || nonce) and cv = hash(commitment || U^ || nonce)

P.S. I'm going to open a pull request to remove the unuseful escape chars and, if you want, update the draft to snake_case notation

@alessandroguggino alessandroguggino changed the title Blind Messages Proof Fix Blind Messages Proof May 11, 2022
@tplooker
Copy link
Member

Hey @alessandroguggino good catch, yes there are some inconsistencies, however you are right that our focus as a WG is primarily on the core draft right now. Feel free to open a PR to address any syntax inconsistencies anything broader we will address once the core draft is complete/stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants