Repository navigation
fix(approach): cover the broader Private Payments use case as an explicit variant - #220
Open
Darkjay123 wants to merge 1 commit into
Open
Darkjay123 wants to merge 1 commit into
Darkjay123 wants to merge 1 commit into
Conversation
…icit variant Per the extension list in issue ethsystems#138: map non-stablecoin rails, CBDC and traditional payment integration onto the existing sub-approaches with pattern differences called out; extend related_use_cases.
rymnc
reviewed
Nov 20, 2026
|
|
||
| ### 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. |
Member
There was a problem hiding this comment.
this line makes three claims that the map does not support.
pattern-private-iso20022says 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-depositssends 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-paymentskeeps "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. |
|
|
||
| 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. |
Member
There was a problem hiding this comment.
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.
|
|
||
| ## [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. |
Member
There was a problem hiding this comment.
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)) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completes the extension list in issue #138 for this card: the broader Private Payments use case becomes an explicit variant.
What changes
approaches/approach-private-payments.md:related_use_casesgainsprivate-payments, and a new Variants subsection under Problem framing maps non-stablecoin rails onto the existing sub-approaches with pattern differences called out: bank deposits and tokenized deposits move the off-ramp boundary from issuer redemption to the issuing bank's ledger, Private ISO 20022 carries message-level privacy toward traditional rails, CBDC deployments trade commercial issuer incentives for central-bank policy over the same shielded-pool or privacy-L2 mechanics. Consumer retail adds merchant acceptance and chargeback paths the shielded-pool sub-approaches do not address.use-cases/private-payments.mdalready links this card, so no change is needed there.CHANGELOG.md:[Unreleased]entry.Checks
The Vale prose gate passes locally on the edited card and all four CI checks are green on this PR.
With this and the four new approach cards in #216-#219, every use case in issue #138's list links to at least one approach.
Part of #138.