You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered: