Privy Labs Protocol Whitepaper v 1.0
  • Privy Labs Protocol
    • Introduction
      • The paradox of social media
      • The persistence of piracy
      • The bottom line
    • Solution Overview
    • Team
  • Our Philosophy & Values
    • 3 Core Tenets
    • Our Why
    • Why Web3
  • Our Approach
    • Problem-solving at the source
      • Core Primitives
      • Copyright - Originality, Creativity, & Fixation
      • The DMCA
      • Removal
  • The Core Technology
    • Systems Overview
      • Virtual Account System
        • Account Abstraction
        • Privacy
        • Gas
      • Content Certificate & Tracking System
        • Proof of Ownership
        • Watermarking
        • Encryption & Cryptography
        • Storage
        • Publicity & Privacy
      • Content Verification Network
        • Permissioned Approval
        • Takedown
  • Use Cases
    • Use Cases
      • Sensitive content: Adult creators, models, & sex workers
      • Content Creators
      • Digital artists & photographers
      • Journalists
      • Families
      • Celebrities
      • Social media platforms & creative marketplaces
      • Trust & Safety Organizations
  • PrivyCam
  • Governance & Community
    • Privy DAO
  • Tokenomics & Incentives
    • Incentive Model
  • Risks & Mitigants
    • Risks & Mitigants
  • Our Roadmap
    • Our Roadmap
Powered by GitBook
On this page
  1. The Core Technology
  2. Systems Overview
  3. Content Certificate & Tracking System

Encryption & Cryptography

PreviousWatermarkingNextStorage

Last updated 1 year ago

For encrypting and decrypting individual pieces of content for storage within the Privy ecosystem, symmetric key encryption is used. Alongside being utilized primarily and actively by federal governments and industry, NIST (National Institute of Standards and Technology) has described AES-256 as by sufficiently large quantum computing, quoting “larger key sizes needed”. For peer-to-peer exchange of encrypted data, we further utilize Diffie-Hellman key exchange. Both AES-256 and the private keys necessary for DHKE are generated locally by the client in an end-to-end encrypted manner.

AES-256
less impacted
on-chain