Hypersign.Id
Hypersign.idEntity StudioIdentity Wallet
  • 💬Welcome!
  • Hypersign KYC
    • Introduction
    • Integrations
      • KYC Service
      • Widget Configuration
      • Environments
        • Development
        • Production
      • Webhook
    • KYC Widget
      • Integrations
        • Backend Integration
          • Generate AccessTokens
          • Generate KYC Session Id
        • Frontend Integration
      • Data Capture
        • Data Vault Setup
        • Capture Facial Recognition
        • Capture ID Document
        • Capture zk-proof and KYC token
        • Capture User Consent
      • User Data
        • idToken
    • Hypersign ID Wallet
    • On-Chain KYC
      • Contracts Deployment
      • Use Cases
      • Supported Blockchains
      • KYC Token Metadata
    • Dashboard
      • User Sessions
      • User Session Details
      • Usage
      • Credit
    • Concepts
      • Facial Recognition
      • ID Verification (via OCR)
      • Reusable KYC
      • Encrypted Data Vault (EDV)
      • Facial Authentication
      • Issuer Marketplace
      • Security
      • Privacy
      • Credentials Types
        • Personhood Credential
        • Passport / Govt. ID Credential
      • zk Proof Types
        • Proof Of Personhood (PoP)
        • Proof Of KYC (PoK)
        • Proof Of Age (PoA)
      • Uniqueness Check
      • Credential Revocability
      • Machine Readable Zone (MRZ)
      • Liveliness Check
      • Zero Knowledge Proof (zkp)
        • Introduction
        • zk-SNARK
        • Circuits
        • SSI and ZKP
    • Tutorials
      • How to Integrate KYC in minutes?
      • How to add your team member?
  • Hypersign SSI
    • Introduction
    • Setup SSI Service
      • Create Your First DID
      • Credits
    • 🔗API Reference
      • Service Authentication API
      • DID
      • Schema
      • Verifiable Credential
      • Verifiable Presentation
        • Presentation Template
        • Presentation
    • 🎰API Playground
    • 🏑SSI Playground
  • Hypersign Developer Dashboard
    • Service
      • Managing API keys
      • Network Fee
    • Members & Roles
      • Members
        • Assign Role To Member
      • Invitations
        • Member Access Admin's Dashboard
      • Roles & Permissions
        • Permissions List
    • Security
      • Login
      • Multi factor Authentication (MFA)
  • Hypersign Identity Network
    • Introduction
    • Validators & Delegators
      • Installation of Node
      • Running a Testnet Validator Node
    • Governance
      • Proposals
        • Blockchain Node Upgrade
        • Community Pool Spend Proposal
        • Blockchain Parameter Change Proposal
        • Text Proposal
      • Delegation
    • Faucet (testnet)
    • Developers
      • HID-Node Codebase
      • ⚙️Setup Local hid-network Tutorial
        • Running one-node local hid network
        • Create and fund new account
        • Transfer funds
        • Connect Keplr to local hid network
      • Hypersign SSI Toolkit
        • Hypersign DID SDK
        • Hypersign Schema SDK
        • Hypersign Verifiable Credential SDK
        • Hypersign Verifiable Presentation SDK
        • OfflineSigner
    • Blockchain & ID Explorer
  • Core Concepts
    • Introduction
    • Decentralized Identifier (DID)
      • DID Registry
      • Private and Public DID
      • DID Authentication
      • DID Communication (DIDComm)
      • Adding multiple controller to DID
      • Adding multiple verification methods
      • Verification Method vs Recovery Signature
      • Blockchain Account Id
      • DID Threshold
      • Verifiable Condition
      • Verification Relationships
        • Authorization Capabilities (zCap)
    • Schema
      • Schema Registry
      • Schema.org
    • Verifiable Credential (VC)
      • Credential Revocation Registry
      • Issuing a Credential to Multiple Subjects
      • Bearer Credential
      • Single-Use Credential
    • Verifiable Presentation (VP)
    • Specifications
      • Supported Signature Algorithms
      • Client Specification
        • EVM based chains
        • Cosmos based chains
  • Ecosystem
    • Forum
    • Github
    • HID Explorer
    • Eiko
    • MetaAuth
  • Privacy Policy
Powered by GitBook
On this page
Edit on GitHub
  1. Hypersign KYC
  2. Concepts
  3. zk Proof Types

Proof Of Personhood (PoP)

Previouszk Proof TypesNextProof Of KYC (PoK)

Last updated 6 months ago

Hypersign’s PoP leverages video KYC and to verify if a specific account (or wallet address) belongs to a real human.

How It Works?

1. Video Capture and Verification

The process begins with a user submitting their video KYC through Hypersign's KYC Widget. Once the video is collected, it undergoes a series of AI-driven checks:

  • Liveness Detection: The AI model uses liveness detection to confirm that the person is physically present in real-time, as opposed to a static image, video replay, or deepfake. This involves subtle movement analysis, such as blinking, head movements, and sometimes following prompts like changing gaze direction or smiling.

  • Anti-Spoofing Measures: The AI model detects spoofing attempts, such as using photos, videos, or masks. Techniques like depth analysis and light reflection analysis differentiate between a real face and 2D images or video screens.

2. Credential Issuance

Once all checks pass, the KYC issuer provides a Personhood Credential. This credential confirms that the user has passed all necessary verifications and includes a digital signature from the issuer. The user then stores the Proof of Personhood credential securely in their data vault.

3. Zero-Knowledge Proof (ZKP) Generation

4. Proof of Personhood Token Generation

Finally, the user submits the Proof of Personhood (PoP) to the issuer's smart contract, requesting a Hypersign KYC Token, which is a Soulbound Token signifying Proof of Personhood. The smart contract verifies the zk proof and mints a token directly to the user’s wallet, establishing a blockchain-backed verification of personhood.

After receiving the credential, the user generates a of it. This proof, also known as the Proof of Personhood (PoP), is created by submitting the credential to a custom-built , where a groth16-based zk proof is generated. This proof maintains privacy while verifying personhood.

zero-knowledge proof (zk proof)
zk circuit
Zero-Knowledge Proofs (ZKPs)