zkMe Dochub
GitHubTwitterDiscord
  • zkMe Network
  • Learn about zkMe Network
    • Introduction
    • Try a Demo
    • High Level Architectural Overview
      • High Level User Stories
      • zkMe Protocol Components
        • zkMe zkVault
        • zkMe DID Method
        • zkMe Credential Suites
        • zkMe Self-Sovereign Identity
    • Vision, Mission & Design Philosophy
    • Value Propositions & Use Cases
  • Verify with zkMe Protocol
    • Integration Checklist
      • zkMe Dashboard Setup
      • zkMe Supported Chains Overview
      • zkMe Protocol Smart Contract
    • Integration Guide
      • JavaScript SDK
        • zkKYC - Compliance Suite
        • MeID - Anti-Sybil Suite
        • Me - Profiling Suite
      • zkMe API
        • zkKYC - Compliance Suite
          • Verify zkKYC Status
          • Get KYT Results
      • Platform Integration
        • QuestN Integration
      • Smart Contract Verification
        • Compliance Suite
      • Customize Widget UI
    • zkKYC - Compliance Suite
      • zkMe zkKYC Levels
      • Regulatory Frameworks
        • EU - MiCA/TFR Regulations
        • US - Crypto Regulations
        • UK - Crypto Regulations
      • zkKYC Credentials
        • Proof-of-Citizenship (zkPoC)
        • Proof-of-Location (zkPoL)
        • Proof-of-Accredited-Investor (zkPoAI)
        • AML Check (AMLMe)
        • Know Your Transaction (KYT)
          • KYT Supported Scope
        • Know Your Business (KYB)
    • MeID - Anti-Sybil Suite
      • CKKS Homomorphic Encryption
      • DID Creation
      • MeID Credentials
        • MeID
    • Me - Profiling Suite
      • MeScores Credentials
        • zkCredit Score
        • zkSocial Network
        • zkDAO Management
        • zkGaming Status
    • zkMe Roadmap
  • Explore More
    • zkMe Bug Bounty Program
    • zkMe Brand Kit
    • zkMe Identity Hub
    • FAQ
    • Glossary
    • Link
      • GitHub
      • X / Twitter
      • Medium
      • YouTube
      • LinkedIn
      • Discord
      • Blog
    • Privacy Policy
Powered by GitBook
On this page
  • Fully homomorphic encryption to protect users' privacy
  • How does it work?
  1. Verify with zkMe Protocol
  2. MeID - Anti-Sybil Suite
  3. MeID Credentials

MeID

The One Face, One MeID approach ensures a rapid and privacy-preserving solution to combat bot and sybil attacks.

PreviousMeID CredentialsNextMe - Profiling Suite

Last updated 8 months ago

Fully homomorphic encryption to protect users' privacy

Fully homomorphic encryption (FHE) is used in zkMe to protect user privacy while encrypting their facial data. This means that user identity can be securely verified without revealing any personal information. With FHE, the facial data is encrypted in such a way that it can be analyzed without being decrypted, making it a powerful privacy-preserving tool. In zkMe, FHE is used during the face graph generation and encrypted face graph cross-check stages to ensure the security and privacy of user data.

How does it work?

  1. Liveness check

  2. Face graph generation

  3. Fully homomorphic encryption

  4. Encrypted face graph cross-check

  5. Unique zkMe DID creation

  6. Final report check

For a visual demonstration of these steps, watch the video below: