Skip to main content
The IPTF Map documents institutional use cases that require privacy-preserving blockchain infrastructure. Each use case describes real business requirements, actors, problems, and recommended technical approaches.

​
Core Use Cases

Private Payments

Cross-border and domestic transfers where transaction details must remain confidential between parties

Private Stablecoins

Institutional stablecoin settlement with stakeholder-only visibility and atomic DvP/PvP

Private Bonds

Confidential bond issuance and trading with atomic delivery-versus-payment settlement

Private Derivatives

ERC-6123 interest-rate swaps with confidential margin balances and settlement amounts

Private Money Market Funds

Tokenized MMFs with private position sizes and redemption patterns

Private Authentication

Prove membership or eligibility without revealing identity or creating linkable activity

​
By Domain

​
Payments

  • Private Payments - Confidential cross-border and domestic transfers
  • Private Stablecoins - Institutional stablecoin settlement infrastructure

​
Funds & Assets

  • Private Bonds - Institutional bond issuance and trading
  • Private Derivatives - ERC-6123 smart derivatives contracts
  • Private Money Market Funds - Tokenized MMFs for treasury management

​
Identity & Compliance

  • Private Authentication - Zero-knowledge credential verification and identity proofs

​
Common Requirements

Across all institutional use cases, several privacy requirements consistently emerge:
Must hide: Amounts, counterparty identities, transaction purpose, timing patternsPublic OK: Network existence, legal entity identities (in some contexts), contract codeRegulator access: Scoped viewing keys, ZK proofs, access logging via attestations
Most institutional use cases require atomic delivery-versus-payment (DvP) or payment-versus-payment (PvP) settlement using standards like ERC-7573.Minutes-level finality is acceptable for institutional pilots and production deployments.
Privacy solutions must maintain:
  • KYC/AML/sanctions compliance
  • Selective disclosure for regulators
  • Books-and-records requirements
  • Jurisdiction-specific frameworks (MiCA, GENIUS, etc.)
  • Predictable L2 costs (post-EIP-4844)
  • Encrypted audit logs with L1 anchors
  • Key rotation and retention policies
  • Production timelines: 1-2 years for most use cases

​
Related Resources

  • Approaches - Detailed solution architectures for each use case
  • Patterns - Reusable technical patterns and primitives
  • Domains - Conceptual organization by business domain

Build docs developers (and LLMs) love

Get started for freeTalk to us