Skip to main content
This section organizes privacy-preserving blockchain patterns by business domain. Each domain page provides a quick reference to relevant use cases, implementation patterns, and technology vendors.
Each domain acts as a thin index to help teams quickly identify the right problems and solutions. For detailed implementations, refer to the linked use cases and patterns.

Domain Areas

Payments

Institutional cash movement, stablecoin transfers, PvP/DvP cash legs with privacy

Trading

Execution privacy, RFQ workflows, pre-trade leakage control, atomic settlements

Custody

Wallet operations, KMS/HSM integration, freeze controls, regulatory access

Identity & Compliance

KYC/AML credentials, attestations, private verification, regulatory disclosure

How to Use This Section

1

Identify Your Domain

Start with the business area that matches your institutional requirements
2

Review Primary Use Cases

Each domain links to the most relevant institutional use cases
3

Explore Implementation Patterns

Follow shortest-path patterns for proven technical approaches
4

Evaluate Vendors

Review adjacent vendors offering solutions in each domain

Cross-Domain Considerations

KYC/AML verification is a prerequisite across all domains. Most institutional workflows require credential verification before any financial operations.
Secure key management and wallet operations underpin payments, trading, and asset management domains. Custody patterns are referenced throughout.
Many domains require cross-chain or cross-asset atomicity (DvP, PvP). ERC-7573 and zk-SPV patterns appear across multiple domains.
  • Primary Use Cases: The main institutional problems each domain addresses
  • Shortest-Path Patterns: Proven implementation approaches with minimal complexity
  • Adjacent Vendors: Technology providers offering relevant solutions
  • Related Domains: Cross-references where domains intersect
Domain pages are intentionally concise. Detailed technical specifications, code samples, and implementation guides are maintained in the use cases and patterns sections.

Build docs developers (and LLMs) love