Additional Context
- The US dollar is on one side of 89% of FX trades (BIS Triennial Survey, April 2025).
- Off-chain, CLS settles FX payments in 18 currencies through payment-versus-payment (PvP) to remove settlement risk.
- Swift announced a blockchain-based shared ledger in September 2025 with a Consensys prototype, and launched an initial live pilot of cross-border tokenized-deposit payments with 17 banks in July 2026; final settlement still runs through existing systems.
Actors
Banks · Payment Networks · Corporate Treasury · Liquidity Providers · Regulators · Stablecoin Issuers
Problems
Problem 1: Trading Intent and Front-Running Prevention
FX markets are highly competitive with tight spreads. Leaked trading intent enables front-running and adverse price movements.
Requirements:
- Must hide: Order size, direction, timing, counterparty relationships
- Public OK: General market liquidity, executed trade existence (after settlement)
- Regulator access: Trade reporting for market surveillance; sanctions screening
Constraints:
- Real-time settlement requirements
- Liquidity fragmentation across stablecoin venues
- Regulatory reporting obligations for FX derivatives: forwards, swaps and options are reportable under EMIR (Art. 9; currency derivatives per MiFID II Annex I C(4)) and Dodd-Frank (OTC FX options are swaps under the CFTC/SEC product definitions; the Treasury FX determination, 2012 exempts FX swaps and forwards from clearing but not trade reporting); spot FX (delivery within two trading days for major pairs, Delegated Regulation (EU) 2017/565 Art. 10; T+2 in US practice.
Problem 2: Cross-Border Settlement Privacy
International payments reveal business relationships and transaction patterns that competitors can exploit.
Requirements:
- Must hide: Payment amounts, sender/receiver identities, payment purpose
- Public OK: Settlement finality confirmation
- Regulator access: AML/CFT monitoring; cross-border transaction reporting
Constraints:
- Multi-jurisdictional compliance requirements
- Correspondent banking relationships
- SWIFT alternative positioning
Recommended Approaches
See Private Trade Settlement for general settlement architecture. FX-specific considerations:
- Privacy-preserving PvP (Payment vs Payment) settlement: Private PvP via ERC-7573 (amount privacy only when the escrow contracts run inside a shielded layer)
- Cross-network settlement options and their recovery paths in Approach: Atomic DvP Settlement
- Stablecoin privacy patterns from Private Stablecoins for Institutional Payments
To keep trading intent out of the public mempool before inclusion (Problem 1), see Approach: Private Transaction Broadcasting.
Open Questions
- How does privacy interact with real-time gross settlement requirements?
- What's the role of central bank digital currencies vs private stablecoins?
- How to handle multi-currency atomic swaps with privacy?
Notes And Links
- Related: Private Stablecoins for Institutional Payments (settlement currency privacy)
- Related: Private Payments (payment privacy patterns)
- Market context: Swift's own blockchain-based shared ledger (tokenized-deposit pilot, July 2026)
- Standards: ERC-7573 (Draft; conditional settlement, atomicity rests on the decryption oracle, hides no amounts or counterparties, no FX rate check), ISO 20022 (messaging)