Import the anon-aadhaar pcd package in the Zupass locally and test the integration

What is the bug?

It seems that the Aadhaar pdf cars is not the main way to handle the Indian citizenship. We need to explore new ways to interact with the Indian Identity that feets more with the actual user journey.

Motivation

After benchmark a few circuits open source implemented on Github(check the issue #16) , The RSA circuit in zk-email-verify have a good performance more than another circuit. We should replace current circuit to zk-email-verify.

Plan

• Clone circuit from zk-email-verify.
• Modify circuit and support RSA signature use sha1 hash function.

What is the bug?

CI doesn't cache file fpr structed setup. This made CI run for very long time.

testing the webhook

Motivation

In current version, prover only need provide a pdf file, however prover must provide password of pdf also to ensure he have permission on this pdf file.

Solution

Researching...

What is the bug?

We miss auto install qpdf for command yarn gen-pdf in pcd packkage

How can it be reproduced? (optional)

Run yarn gen-pdf in pcd package.

What is the feature?

The main flow for now is to extract the modulus (RSA public key) from the PDF, which enables us to test with a random RSA signature. But to check Aadhaar authenticity the inputted modulus must be the official public key.

The feature will consist of boolean parameters initialized in the react context provider, if true it will take the modulus from PDF, if false it will take the official modulus.

Solidity needs to be updated with the circuit's current version

Motivation

We should cache power of tau and circom when run github action.

What is the bug?

Constants variables need to be accessed from one point.

• Change the cert upload to password input
• Change pdf upload flow

For now we can't verify a proof using the SDK in the Zupass repo, because it's not compatible with es2015.

When importing the verify function I have these errors:

✘ [ERROR] Big integer literals are not available in the configured target environment ("es2015")
@pcd/passport-interface:dev: 
@pcd/passport-interface:dev:     ../../../anon-aadhaar/node_modules/wasmcurves/src/bigint.js:107:15:
@pcd/passport-interface:dev:       107 │     return n - 1n;
@pcd/passport-interface:dev:           ╵                ~~

What is the bug?

How we can recover or disable ID card if we lost it?

Research

...

What is the bug?

As we are changing the way to compute the witness, we will to generate a new test PDF that support the same signature type as the original PDF.
This is needing to enhance our unitary tests and enable users to test our tool without an Aadhaar card.

Generate a PDF with the following specs:

• adbe.x509.rsa.sha1
• Signature length: 128
• V = 2
• Password encrypted (optional)

• Android Support
• iOS Support

Motivation

We should support selective disclosure on anon aadhaar. Users/Prover can prove they don't create exist proof, without review her/his(their) all information of him. However, Users/Prover can do it if they hold some private information. Malicious parties can not create this proof because they don't know this information.

We can use this to handle a lot of illegitimate action/transaction.

Solution

Researching...

What is the bug?

Proof is not being created , trapped in error

How can it be reproduced? (optional)

Simple try logging in with Aadhar

Additional context (optional)

This is the error Uncaught (in promise) Error: Not all inputs have been set. Only 96 out of 97

and i think its become zkey json was changed

Problem

We use zkp protocol to create proof for signature. This mean one user can create the proof from his data and share it for other people. We don't know who create this proof but this proof still valid. They can use this proof to cheat our systems. We should think the mechanism to avoid this case.

Relate with #28

Motivation

We can limited number proof user can create. This is useful for avoid spam and DOS attack

Research

We can add RLN circuit to our circuit or think about another solution.

Some types are not compliant with the PCD SDK
Import types from @pcd-types

With web prover we can fetch proving key data from Web server. For testing web prover we should:

• Create mock server to store key.
• Test fetch key from server
• PCD flow should run successfully.

Feature

Currently anon-aadhaar-react doesn't support with react-native. I'm happy to work package for anon-aadhaar-react-native

Error

What is the feature?

These test vectors are needed to directly test our circuit, they make abstraction of the PCD and the typescript implementation.

Additional context (optional)

These vectors will enable testing new frameworks.
Check the following example

What is the bug?

For now, the proving flow is working on browsers but as it is running in the main thread it can cause freezes or even an overflow on not powerful computers/mobiles.

How can it be solved? (optional)

We can try to package the proving flow in a web-worker using this lib.

Create an express server that will serve artifacts for testing webprover

Motivation

The witness gen from the same inputs data is same, we can cache this data and speedup proving time.

Research

🔪

• Scripts need to delete all the temp folders before creating new ones.
• Create folders only when needed.

Motivation

We should proof data we extract from identity sources(from pdf file, website, xml data). The zk-regex is one of good direction we should try.

Plan and expect outcome.

• Understand zk-regex constructions
• Build a few playground examples
• Think how we can apply it to anon-aadhaar project.

As the path is the relative path from the root src folder, when building the package this path is not relevant anymore.

function getVerifyKey() {
  // eslint-disable-next-line @typescript-eslint/no-var-requires
  const verifyKey = require('../artifacts/verification_key.json')
  return verifyKey
}

There is some solutions to this problem:

• Change the way the path is implemented, so the relative path works in src and in build
• Implement a bundler

Motivation

CP-SNARK help we modular prove system on same witness input. This can be good for compose and exchange credential between parties based on same witness about one people without lack privacy.

This also another direction research to improve performance/

A Circom circuits show many warning messages. Let fix circuits and make it better :D

What is the bug?

• Title and Label font color to black
• Add disclaimer and explanation in model
• Improve input file button UI
• Proof component size and display

How can it be reproduced? (optional)

Include steps, code samples, replies, screenshots and anything else that would be helpful to reproduce the problem.

Additional context (optional)

Add any other context about the problem here.