Proof-of-Accredited-Investor (zkPoAI)
Enables privacy-first verification of accredited investor status using Zero-Knowledge Proofs, ensuring compliance without exposing financial or identity details.
User Journey
Alice is interested in participating in a token sale restricted to accredited investors. With zkMe's zkTLS capability, she proves her accredited status based on income thresholds, without sharing any documents or financial details. After a single check, she receives a Proof-of-Accredited-Investor credential as a Soulbound Token (SBT) backed by a zero-knowledge proof. She can now seamlessly access investment opportunities across platforms, while keeping her sensitive data completely private.
See It in Action
Explore how users can prove accredited investor status and get their zkPoAI credential without exposing financial details.
Why zkMe zkPoAI?
Privacy first: Leverage zero-knowledge proofs to confirm accredited investor status without disclosing income or identity details.
Reliable data source: Validate investor eligibility using trusted data for reliable, regulation-aligned accreditation.
Compliance-ready: Fulfil SEC-accredited investor requirements (e.g., income thresholds) with cryptographic compliance built in.
Fully reusable: Once verified, users can reuse their zkPoAI credential across multiple platforms without repeating the verification process.
Decentralized & Secure: No central authority stores sensitive data—proofs are generated and verified without exposing private user information.
Plug-and-play: Easily integrate zkPoAI into your onboarding flow with our Web and Mobile SDKs for instant, secure accreditation checks.
How It Works
The zkPoAI procedure verifies a user's accredited investor status without revealing sensitive personal data. It leverages trusted data sources to confirm income-based eligibility. Combined with zkTLS capability, the process ensures the user’s authenticity while preventing fraudulent activities. Here's a high-level overview of the procedure:
User Income Verification:
Generate QR Code: The zkMe widget generates a unique QR code for income verification.
Scan via Mobile Device: Users scan the QR code using their mobile devices.
Redirect to Portal: Upon scanning, users are automatically redirected to the zkTLS interface via an Instant App, App Clip, or Native App.
Login: Users follow the instructions on the redirected portal to log in via the specified login method.
Authorize Data Sharing: After logging in, users will see a "Share Data" button. By clicking it, they authorize the system to proceed.
Automated Data Retrieval: The system automatically identifies and extracts the required fields (e.g., year, earning data), and prepares them for further processing.
Generate Random Numbers: The user's device generates a random number as part of the zkPoAI process.
Zero-Knowledge Proof (ZKP) protocol:
Commitment Phase: The user generates a cryptographic commitment. This commitment includes hashed information about income without revealing actual coordinates or sensitive data. And the commitment is securely stored on the user's device, ensuring it cannot be tampered with.
Challenge Phase: The verifier (the service or entity performing the verification) selects a random challenge to ensure the user's commitment is valid and sent to the user's device for processing.
Response Generation: The user’s device processes the challenge by combining it with the previously generated random number and the commitment, then sends the response back to the verifier.
Verification: The verifier checks the validity of the response and whether it satisfies the accredited investor criteria, without gaining knowledge of the user's actual coordinates.
Verification Result: Based on the verification outcome, the verifier can check if the user qualifies as an accredited investor, without explicitly obtaining their real address or coordinates.
Pricing & Integration
From startups to scale-ups, our pricing and simple integration are built to support your growth. Drop us a line at [email protected] and let’s kick things off!
Last updated