UniRep Protocol

A Zero-Knowledge Protocol built to handle anonymous user data.

github

website

twitter

discord

This project has been sunset and is not actively worked on anymore.

Overview

UniRep is a zero-knowledge protocol that securely manages user data through anonymous identifiers, enabling trustless interactions and enhanced user privacy in applications. UniRep expands the notion of reputation to include various user data aspects, such as preferences, activity, alignments, and ownership.

Using anonymous identifiers (epoch keys), the protocol allows for trustless engagement with applications while preserving user privacy. This approach promotes non-custodial applications that don't hold user data, reducing data breach risks and emphasizing security for both users and developers.

UniRep was originally proposed by BarryWhiteHat in this ethresear.ch post.

Features

UniRep aims to be the ultimate foundation for constructing tailored, yet fully compatible, zero-knowledge (zk) applications. It functions as a powerful memory layer for zk, offering private, non-repudiable data storage and retrieval capabilities. With UniRep, users can effortlessly receive data, prove facts about their information, and store the results while enjoying robust privacy assurances. The protocol empowers developers to create bespoke zk applications without compromising on interoperability and efficiency.

Key UniRep features include:

Data Storage: Unirep allows small amounts of data to be associated with anonymous users. Applications can conditionally associate data, like requiring a user to prove control of an Ethereum address before attesting to it.
Extensible Proofs: The system is designed to be extended with custom application logic. For example, an application might require proof of Ethereum address control to sign up.
Trustless Interoperability: Applications can interconnect by having users create proofs using publicly available state.
No Forced Data Sharing: Unirep applications cannot see what data belongs to what user, unless the user reveals it. User data also cannot be changed unless the user provides the application with an epoch key.