Please leave your feedback here!!!

Please give some information about bug reports or feature requests.

If reporting a bug, make sure to specify the device model, what ID you have (passport or ID card), which country your ID is from, and the version of the app.

Please make sure that you never include sensitive information in your posts.
To leave anonymous feedback, make sure you are not signed into an account.

Urgent…

I am a security researcher trying to submit a Critical Vulnerability, but I am currently blocked by the ZK Passport KYC process due to a hardware limitation. The Issue: The ZK Passport app requires an NFC scan of a passport or ID card. Passport: My valid passport is an older version that does not have an NFC chip. National ID: My Indian Aadhaar card does not support NFC scanning. Impact: I am physically unable to complete the verification flow on the mobile app because my valid government documents do not have the required chips. Request: Please allow me to verify using an alternative method (such as manual document upload or a standard video KYC provider like SumSub) that does not require NFC. I have my documents ready to upload immediately.

THANSEER KP About 2 months ago

1
💡

Feature Request

ID Document Not Scanning & Very Slow Processing

Issue type: Bug report Device model: Samsung Galaxy Note 10+ Operating system: Android 12 ID type: National ID card Country of ID: Pakistan App version: 0.9.40 Description of the issue: I am unable to complete identity verification in the zkPassport app because the application fails to properly scan my ID document. The camera scan either does not detect the ID card or remains stuck during the scanning step. Additionally, the verification process is extremely slow. After attempting to scan the ID, the app remains in a processing state for a long time without completing the step or providing a clear error message. I have attempted multiple retries and basic troubleshooting steps, including restarting the app and device and using a stable internet connection, but the issue persists. Expected behavior: The app should successfully scan the ID document and complete verification within a reasonable processing time. Actual behavior: The ID document is not scanned successfully, and the verification process becomes very slow or stuck during processing. Impact: This issue prevents completion of mandatory identity verification required by third-party platforms and blocks time-sensitive verification-dependent actions. Additional notes: I am available to provide additional non-sensitive technical details if required to help resolve this issue.

Muazam Shahzad 2 months ago

1

🪳 Bug Reports

What if someone scans your passport into their ZKPassport App?

This is more of a question than a request. I am building a (experimental) voting platform and currently thinking through attack vectors. In this case, what if an individual is able to access your passport temporarily; long enough to scan it into their ZKPassport App, after which point they lose access to the physical passport. Would the passport owner have any recourse to invalidate the attacker’s scan (presumably by re-scanning it themselves?)? If not … do scanned passports expire in the app (requiring re-scanning) so that the attacker’s version becomes invalid after a certain period (hopefully less than expiration date of the passport)? If not, is there anything that can be done at the application level, such as detecting that proof A uses a passport more recently scanned than proof B? Thanks for the consideration!

Mitchell Douglass 4 months ago

1
💡

Feature Request