Repository navigation
fix(approach): cover the broader Private Payments use case as an explicit variant #220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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. | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this line makes three claims that the map does not support.
suggestion:
Suggested change
|
||||||
|
|
||||||
| 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. Choose a reason for hiding this commentThe 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" ( suggestion: state the gap here, and add it to open questions without a prescribed answer. |
||||||
|
|
||||||
| ## Approaches | ||||||
|
|
||||||
| ### L1 Shielded Payments | ||||||
|
|
||||||
There was a problem hiding this comment.
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.mdasks for one.suggestion: