IPTF
Domain

Custody

Wallet ops/KMS/HSM, freeze/blacklist controls, segregation, recovery, post-trade hooks. - Governed regulator access (view keys / proofs) and evidence logging.

0
Case Studies
2
Patterns
1
Vendor
Custody Data & Oracles Funds & Assets Identity & Compliance Payments Post-Quantum Threats Trading
Shortest-path Patterns

Building blocks for custody privacy

Selective disclosure (viewing keys + zero-knowledge proofs)

Provide on-demand, scoped visibility into confidential trades and positions via threshold-controlled viewing keys or zero-knowledge predicate proofs that answer specific regulator questions. The institution keeps plaintext private by default and releases only the minimum information required to satisfy a specific, logged mandate.

CR: Medium OS: Partial P: Full S: Medium

Atomic DvP via ERC-7573 (cross-network)

Enable atomic Delivery-versus-Payment across two networks so that either the asset is delivered and payment is completed, or the asset returns to the seller. The pattern targets institutions that need cross-network settlement with predictable failure behavior, auditability, and optional privacy extensions layered on top.

CR: Medium OS: Partial P: None S: Medium
Vendors

Who builds custody privacy tooling

Paladin
Open-source (Apache-2.0) privacy layer under the [Linux Foundation Decentralized Trust](https://github.com/LFDT-Paladin/paladin). Paladin provides the common wallet/vault functions that are needed to interact with all forms of privacy preserving smart contracts. It also provides a model for atomic programmability across these privacy preserving smart contracts, harnessing the power of the underlying EVM shared ledger.