ZKP2P
  • Introduction
    • 🐣ZKP2P
  • User Guides
    • For Buyers
      • Complete Guide to Onboarding with ZKP2P
      • Handling Verification Issues as a Buyer
    • For Sellers
      • How to Provide Liquidity and Sell USDC
      • How to Update USDC Conversion Rates
      • Handling Manual Releases as a Seller
      • TradingView Links for Setting Conversion Rates
      • Calculating APR
  • Developer
    • 📔The ZKP2P V2 Protocol
    • 📜Smart Contracts
      • Escrow
        • IEscrow
      • IPaymentVerifier
      • ⛓️Deployments
    • 🌎PeerAuth Extension
      • 🖥️zkTLS
    • Gating Service
    • 🤝Integrate ZKP2P
    • 🏗️Build a New Provider
    • 🔓Security
    • 😬Risks
    • 🤔FAQ
    • 🦺Privacy and Safety
  • 🔖Resources
    • 👨‍💻Team
    • 🐦Twitter
    • 💻Github
    • 💬Telegram
    • 💹ZKP2P
Powered by GitBook
On this page
  1. Developer

Security

PreviousBuild a New ProviderNextRisks

Last updated 3 months ago

ZKP2P is currently in its alpha stage and should be used at your own risk. Our circuits have been audited by PSE. We have outlined known potential risks associated with using the protocol, acknowledging that there may be additional risks not yet identified.

Audits

  • ZKP2P alpha circuits have been audited by

  • Reclaim circuits that are used in our zkTLS flows are

🔓
PSE
audited by ZKSecurity