It’s labor intensive and personally invasive to provide private information to web2 platforms and financial institutions.
We built zkDocs to improve these workflows via cryptographic commitments and zero-knowledge proofs.
github.com/a16z/zkdocs
More info👇
Conversation
Replying to
zkDocs are zero-knowledge enabled documents which allow document verifiers to specify a schema of fields and constraints.
Submitters can create a zk-proof that the information has been submitted truthfully and satisfies certain properties without leaking excessive information.
1
14
When deployed to a public blockchain, the data required to verify a zkDoc schema submission is publicly available, and fully auditable, while always remaining private.
1
1
9
zkDocs achieve the following properties:
1) selectively reveal fields to only relevant attesters
2) publicly verify properties about a submitter’s data, without data visibility
3) shift verification workload from the document verifier to document submitter
1
10
Our codebase includes
- JSON schema -> SNARK Circuit transpiler
- EVM smart contract for commitment storage to ensure data availability
- Browser based client for rendering schemas and to interface with the on-chain contract
1
1
8
zkDocs enable a wide range of applications come online. Some ideas:
- Instantaneous college applications
- Discounted protocol rates to users trusted within an on- or off-chain community
- On-chain collateralization of off-chain assets (e.g. Maker RWA)
1
1
11
A blog post diving into more detail can be found here, or check out the readmes in the repo.
2
1
17
Hey - assuming we get there on individuals retaining private information for NEW applications. Have you written anything or can reference materials on how the world may look where we maintain OLD applications that still have this information with the NEW apps?
