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
  • Escrow
  • Verifiers
  • Nullifier Registry
  1. Developer

Smart Contracts

PreviousThe ZKP2P V2 ProtocolNextEscrow

Last updated 4 months ago

Escrow

The Escrow contract is designed to orchestrate the interaction between different actors in the ecosystem. It manages user registrations, deposits, and transaction intents, and employs Zero-Knowledge Proofs for validation purposes. Additionally, it provides mechanisms for dispute resolution, instant verification, and governance controls to maintain system integrity and ensure a secure and trustless environment for P2P transactions.

Verifiers

The Verifiers are contracts designed to verify and process on-chain proof of off-chain transactions, ensuring they conform to specified protocols. It validates various elements of the transactions including transaction amount, timestamp, recipient ID and intent hash. Through these validations, it facilitates secure transaction processing in the system.

Verifiers conform to a BasePaymentVerifier . For an example of an implemented payment verifier, please check .

Nullifier Registry

The NullifierRegistry is a smart contract that records unique identifiers (nullifiers) to prevent duplication in actions like user registrations. It controls writer permissions for adding nullifiers and offers transparent logging of these actions through emitted events.

📜
specification
here