diff --git a/CHANGELOG.md b/CHANGELOG.md index a6b8c50..d2115a5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,7 @@ All notable changes to the EthSystems Map are documented here. ## [Unreleased] +- fix(approach): [Private Payments](approaches/approach-private-payments.md) covers the broader [Private Payments](use-cases/private-payments.md) use case as an explicit variant, per the extension list in issue #138: non-stablecoin rails, CBDC and traditional payment integration are mapped onto the existing sub-approaches with pattern differences called out, and `related_use_cases` is extended. - fix(approach): review of [Private Transaction Broadcasting](approaches/approach-private-broadcasting.md), with a new Private Relay sub-approach. Review of the patterns, vendors and use cases it links. [Threshold-Encrypted Mempool](patterns/pattern-threshold-encrypted-mempool.md) censorship resistance moves from `high` to `medium` ([#213](https://github.com/ethsystems/map/pull/213)). - feat(approach): [Private Institutional Messaging](approaches/approach-private-messaging.md), filling the "Approach TBD" gap on [Private Messaging](use-cases/private-messaging.md), whose recommended-approaches section now links to the card. Compares anchored off-chain messaging (documented, I2I), mixnet-routed messaging (concept) and on-chain encrypted channels (concept), with a 10-row comparison matrix, persona perspectives, a conditional recommendation and open questions. ([#215](https://github.com/ethsystems/map/pull/215)) - feat(use-case): [Private Tokenized Deposits](use-cases/private-tokenized-deposits.md), bank deposits as claims on a shared ledger: payment privacy between banks, the interbank settlement leg, and the link to the core banking system. Linked from [Private Stablecoins](use-cases/private-stablecoins.md), the [Private Payments](approaches/approach-private-payments.md) approach and the [Payments](domains/payments.md) domain. Adds RTGS to the [Glossary](GLOSSARY.md) ([#214](https://github.com/ethsystems/map/pull/214)) diff --git a/approaches/approach-private-payments.md b/approaches/approach-private-payments.md index 2201592..cf70a73 100644 --- a/approaches/approach-private-payments.md +++ b/approaches/approach-private-payments.md @@ -4,7 +4,7 @@ status: ready last_reviewed: 2026-10-05 use_case: private-stablecoins -related_use_cases: [resilient-disbursement-rails, private-treasuries, private-tokenized-deposits] +related_use_cases: [resilient-disbursement-rails, private-payments, private-treasuries, private-tokenized-deposits] primary_patterns: - pattern-shielding @@ -81,6 +81,12 @@ A multinational bank executes daily institutional stablecoin transfers (USDC, EU - Adversarial-jurisdiction rail has no client-side ZK, no reliable internet, EAL4+ smartcard envelope - Organizational separation between identity-layer operator and field partner is mandatory for the disbursement rail +### Variants + +This card's coverage extends to the broader [Private Payments](../use-cases/private-payments.md) use case, of which stablecoin settlement is the principal instance. Non-stablecoin rails follow the same sub-approach menu with pattern differences: bank deposits and tokenized deposits move the off-ramp boundary from issuer redemption to the issuing bank's ledger, [Private ISO 20022](../patterns/pattern-private-iso20022.md) carries message-level privacy toward traditional rails, and CBDC deployments trade the issuer's commercial incentives for central-bank policy, with the same shielded-pool or privacy-L2 mechanics underneath. + +Consumer retail adds merchant acceptance, chargeback and dispute-resolution paths that the shielded-pool sub-approaches do not address; consumer deployments therefore lean on viewing-key disclosure combined with existing rail integration rather than treating the shielded pool as the consumer interface. + ## Approaches ### L1 Shielded Payments