zkpstandard / zkreference

The official repository hosting the ZKProof Community Reference & Proposals documents.
https://community.zkproof.org/c/zkproof-2019
102 stars 12 forks source link

Clarify the public vs. non-public aspect of “common” in CRS #4

Closed luisbran closed 4 years ago

luisbran commented 5 years ago

Proposed contribution: Clarify the distinction between common (as in shared between prover and verifier) and public knowledge (as in known externally). The lack of distinction was noticed in several parts of the document, when thinking of a comparison between transferable vs. non-transferable ZK proofs. CRS is sometimes being defined as public, although in practice it could be obtained as common to the intervening parties, yet private to a particular interaction. For example, line 177 says “common public input” when first talking of a "common reference string", but the “public” aspect is arguable – being public vs. common-but-not-public may make the difference between transferability vs. non-transferability.

Related locations: Mostly in Chapter 1, starting in section 1.2; will also check for other applicable cases across the document.

Proposed contributors: NIST-PEC team (Luís B, René P, Angela R).

Contribution context: proposed in the "NIST comments on the initial ZKProof documentation" (April 06, 2019) --- item C11.

luisbran commented 5 years ago

Our initial contribution is detailed in section 4 ("Proposal about CRS as public or not") of the "NIST-PEC contributions to advance the draft ZKProof Community Reference from version 0.1 to 0.2"

luisbran commented 5 years ago

We updated the text of our contributions on Oct 10, 2019