Hello Magicians, I am excited to share our latest work with you!
Abstract
This EIP introduces an on-chain registry system for storing abstract statements, where the state of the system can be proven in zero knowledge without disclosing anything about these statements. Developers may use the singleton EvidenceRegistry contract to integrate custom business-specific registrars for statement processing and proving.
Motivation
The standardization and aggregation of provable statements in a singleton on-chain registry significantly improves reusability, scalability, and security of the abundance of zero knowledge privacy-oriented solutions. The abstract specification of the registry allows custom indentity-based, reputation-based, proof-of-attendance-based, etc., protocols to be implemented with little to minimal constraints.
The given proposal lays the important foundation for specific solution to build upon. The more concrete specifications of statements and commitments structures are expected to emerge as separate, standalone EIPs.
Specification
Check out the full specification on GitHub:
The complete reference implementation can be found here.
Would love to see an insightful discussion rolling!
How might the ERC-7812 standard address interoperability challenges among different privacy-oriented protocols while maintaining strict data privacy guarantees?
The EIP is designed to provide a unified provable on-chain storage for all the protocols that integrate with the EvidenceRegistry. For example, there may be a Registrar that manages the ICAO masters list (for on-chain national passport verification). Any protocol that wants to prove the validity of a passport will be able to reference the evidence registry and prove that one of the masters has signed a passport.
The specific business use cases and their implementation are outsourced to the registrars. This means there may be general-purpose “social”, “passport”, and “POAP” registrars that standardize how to manage and prove their data. We think that the behavior of registrars may even be described as separate EIPs.
Every registrar is expected to provide their own means of secure data proving (e.g. on-chain ZK verifier).