Conversation
| @@ -0,0 +1,177 @@ | |||
| # Approach: Private Delivery-versus-Payment (DvP) | |||
There was a problem hiding this comment.
I think for this one we said private-dvp is not a use case, but something that touches multiple use cases. Do you think it still makes sense as an approach?
|
|
||
| ### Recommended Architecture: Privacy L2 + Atomic Settlement | ||
|
|
||
| **Primary Pattern:** [ERC-7573 DvP](../patterns/pattern-dvp-erc7573.md) |
There was a problem hiding this comment.
Is this enough? Do we not need to make this ERC privacy-preserving?
| - EAS attestation logging for audit trails | ||
| - Time-bounded viewing keys for regulatory access | ||
|
|
||
| ### Vendor Recommendations |
There was a problem hiding this comment.
How prescriptive do we want to be at this stage?
Don't think below is bad, just wondering how prescriptive we want to be here at this stage
Also considering trade-offs
E.g. Aztec not live yet, ACE seems a bit diff from atomic settlement, Circle needs to work on L2 etc
|
|
||
| ### Open Questions | ||
|
|
||
| 1. **Stablecoin Issuer Adoption:** Timeline for major issuers (Circle, Tether) to support privacy L2s natively? |
There was a problem hiding this comment.
I see some of above Qs answered
oskarth
left a comment
There was a problem hiding this comment.
This is great! Some minor comments but think we can merge this; definitely better than what we have right now
|
I'll go ahead and merge it; can address above in follow up PRs |
Added detailed, production-ready approaches following a consistent structure:
approach-private-auth.md- ZK-based identity verification using Merkle tree membership proofsapproach-private-derivatives.md- ERC-6123 derivatives with confidential margin & settlement using ZK shielded balancesapproach-private-dvp.md- Delivery-vs-payment with privacy L2 integration and ERC-7573 coordinationapproach-private-l2-stablecoins.md- Native stablecoin infrastructure on private L2sapproach-shielded-stablecoins.md- L1 shielded pools for high-value institutional stablecoin transfersEnhanced Patterns (4 new, 3 refactored)
New Core Patterns:
pattern-co-snark.md- Multi-party ZK proofs for private compliance verificationpattern-privacy-l2s.md- Privacy-native rollups (ZK/FHE) for confidential executionpattern-private-vaults.md- Intent-based portfolio management with encrypted strategiespattern-shielding.md- Foundational ERC-20 shielding with selective disclosureRefactored/Consolidated:
approachesNew Vendor Profiles
orion-finance.md- Private portfolio management with FHE encryptionzama.md- FHE SDK for confidential smart contracts