Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the entry has no pr link. .claude/CLAUDE.md asks for one.

suggestion:

Suggested change
- 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): [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. ([#220](https://github.com/ethsystems/map/pull/220))

- 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))
Expand Down
8 changes: 7 additions & 1 deletion approaches/approach-private-payments.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line makes three claims that the map does not support.

  • pattern-private-iso20022 says that the iso instruction layer is off-chain and stays under bank-to-bank confidentiality. the pattern hides the cash leg. it does not make the message private.
  • private-tokenized-deposits sends only problem 1 to this card. the interbank leg and the link to core banking go to other patterns. plain bank deposits are not on chain.
  • private-payments keeps "how do cbdcs with privacy compare to private stablecoins?" as an open question. this line answers it without a source.

suggestion:

Suggested change
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.
This card's coverage extends to the broader [Private Payments](../use-cases/private-payments.md) use case. For tokenized deposits, the sub-approaches cover payment privacy on the shared ledger. The interbank leg and the link to core banking are in [Private Tokenized Deposits](../use-cases/private-tokenized-deposits.md). [Private ISO 20022](../patterns/pattern-private-iso20022.md) binds ISO 20022 instructions to a cash leg that settles privately. How CBDC privacy designs map onto these sub-approaches is an open question in the use case.


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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the gap is real. no sub-approach covers chargebacks or disputes. but the gap applies to all six sub-approaches, and this line names only the shielded-pool ones. a viewing key "grants read access" (pattern-user-controlled-viewing-keys). it does not reverse a payment, so the "therefore" does not follow. also, the l1 shielded payments sub-approach at line 132 treats the pool as an end-user wallet.

suggestion: state the gap here, and add it to open questions without a prescribed answer.


## Approaches

### L1 Shielded Payments
Expand Down
Loading