A standard interface for a "Verifier Registry"'" contract, through which all zk-SNARK verification activity can be registered.
The following standard allows for the implementation of a standard contract API for the registration of zk-SNARKs ("Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge"), also known as "proofs", "arguments", or "commitments".
TODO: Which functionality is exposed in this standard interface?
zk-SNARKs are a promising area of interest for the Ethereum community. Key applications of zk-SNARKs include:
A standard interface for registering all zk-SNARKs will allow applications to more easily implement private transactions, private contracts, and scaling solutions; and to extract and interpret the limited information which gets emitted during zk-SNARK verifications.
:warning: TODO: Explain the motivation for standardizing a registry, other than simply standardizing the verifier interactions.
⚠️ TODO: Explain the benefits to and perspective of a consumer of information. I.e. the thing that interfaces with the standard verifier registry.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
⚠️ TODO: Add Rationale section.
⚠️ TODO: Add Backwards Compatibility section.
Truffle tests of example implementations are included in this Repo.
⚠️ TODO: Reference specific test cases because there are many currently in the repository.
Detailed example implementations and Truffle tests of these example implementations are included in this Repo.
⚠️ TODO: Update referenced verifier registry implementations so that they are ready-to-deploy or reference deployed versions of those implementations. At current, the referenced code specifically states "DO NOT USE THIS IN PRODUCTION".
⚠️ TODO: Provide reference to an implementation which interrogates a standard verifier registry contract that implements this standard.
⚠️ TODO: Update references and confirm that each reference is cited (parenthetical documentation not necessary) in the text.
Standards
ERC-20 Token Standard. ./eip-20.md
ERC-165 Standard Interface Detection. ./eip-165.md
ERC-173 Contract Ownership Standard (DRAFT). ./eip-173.md
ERC-196 Precompiled contracts for addition and scalar multiplication on the elliptic curve alt_bn128. ./eip-196.md
ERC-197 Precompiled contracts for optimal ate pairing check on the elliptic curve alt_bn128. ./eip-197.md
Ethereum Name Service (ENS). https://ens.domains
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels. https://www.ietf.org/rfc/rfc2119.txt
Copyright and related rights waived via CC0.