Privacy & Zero-Knowledge
1. Zero-Knowledge Proof (ZK Proof)
A cryptographic method that allows you to prove you have certain attributes (like a trust score above a threshold) without revealing the exact values. ZK proofs enable privacy-preserving verification where verifiers can confirm claims without seeing underlying data.
Key Properties:
Completeness: Valid proofs are always accepted
Soundness: Invalid proofs are always rejected
Zero-Knowledge: Verifier learns nothing beyond what's being proven
2. Proof Types
AnyLayer supports four main proof types, each serving different privacy needs:
Threshold
Prove score ≥ X without revealing exact value
"My score is at least 5000"
High
Range
Prove score is between X and Y
"My score is between 3000-5000"
Medium
Exact
Prove exact score value (reveals the number)
"My score is exactly 4500"
Low
Membership
Prove membership in a tier or category
"I'm in Gold tier"
High
Example:
Threshold Proof: "I have a trust score ≥ 3000" (hides exact score)
Range Proof: "My score is between 3000-4000" (hides exact value)
Exact Proof: "My score is 3,450" (reveals exact value)
Membership Proof: "I'm in Gold tier" (hides exact score)
3. Proof Categories
ZK proofs are organized into categories based on what they prove:
Reputation
Prove trust score without revealing exact value
Score threshold, tier membership
Wallet
Prove wallet age and account history
Wallet age ≥ X days, transaction count
Assets
Prove token or NFT holdings
Token balance ≥ X, NFT ownership
Trade
Prove trading volume and activity
Trading volume ≥ X, swap count
Liquidity
Prove liquidity provision
LP position tenure, TVL amount
Lend & Borrow
Prove lending/borrowing history
Health factor, liquidation-free history
Yield
Prove staking and farming participation
Staking duration, yield earned
Cross-chain
Prove multi-chain activity
Bridge volume, chain diversity
Invest
Prove launchpad participation
IDO involvement, investment amount
Protocol
Prove interaction with protocols
Protocol count, interaction history
4. Proof Expiration
ZK proofs have expiration periods to ensure they reflect current data. You choose the expiration when generating a proof:
Short-Term
7 days
Sensitive applications, high security needs
Highest
Standard
30 days
Most common use cases (default)
Balanced
Long-Term
90 days
Stable scores, convenience-focused
Lower
How Expiration Works:
Proofs expire after the selected duration (7, 30, or 90 days)
Expired proofs cannot be verified
You must generate a new proof after expiration
Expiration date is visible in proof metadata
Example:
Proof generated: January 1, 2025
Expiration selected: 30 days
Proof expires: January 31, 2025
After expiration: Proof status changes to "expired" and cannot be used
5. Proof Status
ZK proofs have different statuses throughout their lifecycle:
Pending
Proof generation in progress
No
Verified
Proof successfully verified and active
Yes
Failed
Proof generation or verification failed
No
Expired
Proof has passed its expiration date
No
Revoked
User manually revoked the proof
No
6. Privacy Levels
Proofs can have different privacy levels that control what information is revealed:
Minimal
Maximum privacy
Only the claim being proven (e.g., "score ≥ 5000")
Standard
Balanced privacy
Claim + basic metadata (timestamp, category)
Maximum
More context shared
Claim + additional context (protocol, chain)
7. Privacy-Preserving
A design principle where user data remains private. In AnyLayer, raw data stays local while only proofs or commitments are shared. The system never sees your exact scores, balances, or transaction details.
What's Hidden:
Exact trust score values (in threshold/range proofs)
Individual score components (wallet age, achievements breakdown)
Token balances and amounts
Transaction history details
Personal wallet addresses (when using AnyLayer IDs)
What's Revealed:
The claim being proven (e.g., "score ≥ 5000")
Proof expiration date
Proof category and type
Verification status
8. Selective Disclosure
The ability to share only specific information with verifiers while keeping other data private. For example, proving "score > 3000" without revealing your exact score, wallet age, or achievement details.
Benefits:
Share only what's necessary
Maintain privacy of other data
Control information disclosure
Build trust without oversharing
9. Proof Generation
The process of creating a zero-knowledge proof from your data. Happens locally in your browser or dashboard, ensuring your raw data never leaves your device. The proof is then submitted to the system for verification.
Steps:
Select proof type and parameters
System fetches your data (score, balances, etc.)
Proof is generated locally using cryptographic circuits
Proof is submitted for verification
Once verified, proof becomes usable
10. Proof Verification
The process of verifying that a zero-knowledge proof is valid without seeing the underlying data. Done on-chain via smart contracts or by third-party verifiers. Verification confirms the proof is mathematically valid without revealing your data.
Verification Methods:
On-Chain: Verified by smart contracts (ZKVerifier)
Off-Chain: Verified by verifier network
Hybrid: Combination of both methods
11. Proof Revocation
The ability to invalidate a previously generated proof, useful when you want to withdraw consent or update your verification status. Once revoked, the proof cannot be used for verification.
Reasons to Revoke:
Privacy concerns
Score changes significantly
Want to generate new proof with different parameters
Security concerns
12. Proof Usage Tracking
Proofs track how and where they're used:
Usage Count: Number of times the proof has been verified
Usage Protocols: List of protocols that have used the proof
Last Used: Timestamp of most recent usage
Max Usage: Optional limit on how many times a proof can be used
Privacy Note: Usage tracking helps you monitor where your proofs are being used while maintaining privacy of the underlying data.
13. On-Chain Proof Sync
Proofs can be synced to the blockchain for public verification:
On-Chain Synced: Whether proof is registered on-chain
On-Chain Tx Hash: Transaction hash of on-chain registration
Last Sync: Timestamp of last sync
Public Visibility: Whether proof appears in explorer
Benefits:
Publicly verifiable without querying database
Immutable proof record
Transparent verification
Decentralized trust
14. Proof Explorer Visibility
Proofs can be made public or private:
Public: Visible in AnyLayer Explorer for others to view
Private: Only visible to you and protocols you share with
Explorer Visible: Controls whether proof appears in public explorer
Use Cases:
Public: Showcase your reputation, build trust publicly
Private: Share only with specific protocols, maintain privacy
Last updated