Cowrie Research

zkp2p

2 min read

ZKP2P

  • Name: ZKP2P
  • URL: https://docs.peer.xyz/protocol/zkp2p-protocol
  • Tags: ethereum-ecosystem
  • Category: proof-backed fiat-settlement middleware / zkTLS payment-attestation system / escrowed release infrastructure
  • Summary: ZKP2P is proof-backed release plumbing for fiat-to-crypto trades. The point is the settlement stack: escrowed liquidity, payment evidence, attestation, and release policy. Not a broad ramp note.
  • What it does:
    • Lets sellers deposit onchain token liquidity while buyers pay them offchain in fiat or other offchain payment platforms
    • Locks liquidity through an intent/orchestration flow, then releases tokens when a valid proof of offchain payment is attested and verified
    • Supports multiple proof primitives including zkEmail, TLSNotary, proxy-based zkTLS approaches like Reclaim, and a path toward TEEs
    • Uses an offchain Attestation Service to normalize provider proofs into a standard EIP-712 PaymentAttestation format for onchain verification
    • Adds configurable gating, oracle-driven or delegated rate management, pre-intent hooks, referral/manager fee routing, and multi-orchestrator support around settlement
  • Key claims:
    • The useful move is turning proof of payment into a modular settlement stack rather than one app-specific flow.
    • V3’s offchain Attestation Service is the live choke point. It validates provider proofs, normalizes them, and signs the EIP-712 attestation the contracts consume.
    • UnifiedPaymentVerifierV2 matters because release policy sits there: signatures, nullifiers, snapshots, and release caps.
    • This is not a neutral escrow. Gating hooks, whitelist checks, and rate-manager policy all decide who can lock liquidity and on what terms.
    • The docs are honest enough to keep: some proof paths still depend on hosted notaries, proxies, and future-tense decentralization claims.

Internal linkages

  • Keep this on the strongest upward proof-stack reads: tlsnotary, reclaim-protocol, and vlayer.
  • That is enough. This note is about proof-backed release, not every ramp or authorization sidecar.

Control surface

Graph View