Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project MoPerf: Finding the limits of client-side proving on mobile #57

Closed
4 of 9 tasks
oskarth opened this issue Jan 26, 2024 · 3 comments
Closed
4 of 9 tasks

Comments

@oskarth
Copy link
Collaborator

oskarth commented Jan 26, 2024

This is a milestone issue for the ~1-3 week MoPerf project.

Context: See https://hackmd.io/5ItB2D50QcavF18cWIrmfQ?view=.

Problem

For ZK-ID solutions like Anon-Aadhaar to be useful in the real world they need: (a) a significant amount of constraints (~1m) and (b) to work reliably on mobile for many users.

Currently PoC written for anon-aadhaar and mopro (pocket-aadhaar), while better than the status quo, only target ~160k constraints. As this gets increased to 1.7m (current status of Anon-Aadhaar circuits; can possibly be optimized to ~1m) many independent technical risks related to performance arise.

This is also true for other ZK Identity solutions. Without going into too much detail, this is due to having to perform a SHA256 hash of fields inside the artifact (PDF) for computing the nullifier (~800k constraints). This is in addition to the RSA verification check (~160k constraints).

Currently, we don't know exactly what is feasible on mobile. This means projects such as an Anon-Aaadhaar Showcase App (link) come with too many technical risks to execute in a short time period with confidence.

The big question we want answer is: What is a reasonable size of a circuit (primarily number of constraints, but other factors too) that we can run on mobile?

Issues

These should be separate issues.

Acceptance criteria

Above issues addressed and report published somewhere.

@oskarth
Copy link
Collaborator Author

oskarth commented Feb 21, 2024

See https://hackmd.io/5ItB2D50QcavF18cWIrmfQ?view= for report. Missing Android numbers but basically done.

@vivianjeng
Copy link
Collaborator

See https://hackmd.io/5ItB2D50QcavF18cWIrmfQ?view= for report. Missing Android numbers but basically done.

android numbers are added

@oskarth
Copy link
Collaborator Author

oskarth commented Feb 21, 2024

Consider this project done, closing issue.

@oskarth oskarth closed this as completed Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants