feat(pattern): add Atomic DvP Settlement pattern#56
Conversation
oskarth
force-pushed
the
pr-009-dvp-atomic-settlement
branch
2 times, most recently
from
32f3de2 to
2d799ea
Compare
| @@ -0,0 +1,182 @@ | |||
| --- | |||
There was a problem hiding this comment.
These already exist pattern-dvp-erc7573.md.
Is this new pattern a replacement or an extension to the previous pattern?
| 5. **Settle**: If conditions satisfied, escrow atomically transfers asset to buyer, payment to seller. | ||
| 6. **Timeout**: If conditions not met by deadline, escrow returns assets to original owners. | ||
|
|
||
| ## Integration with EIP-6123 (Derivatives) |
There was a problem hiding this comment.
This could be promoted to /approach.
Addressed Feedback@Meyanis95✅ Promoted to approach - Content documents multiple mechanisms (HTLC, escrow, oracle), which fits approach format better than pattern ✅ Added relationship clarification - Overview now explains this is general atomic settlement, while ERC-7573 pattern handles cross-network specifically ✅ Added persona TLDRs - Business, Technical, Legal summaries per approach template Ready for re-review. |
|
|
||
| Settlement risk occurs when one party delivers an asset without receiving payment, or vice versa. This approach documents multiple mechanisms for achieving atomic settlement where both legs complete or neither does, eliminating counterparty risk. | ||
|
|
||
| **Relationship to [Atomic DvP via ERC-7573](../patterns/pattern-dvp-erc7573.md)**: The ERC-7573 pattern specifically addresses cross-network coordination using the ERC-7573 standard. This approach is more general, documenting the core atomicity mechanisms (HTLCs, escrow, oracles) that work on single networks or can be composed with ERC-7573 for cross-network scenarios. |
There was a problem hiding this comment.
ERC-7573 is still a draft
|
|
||
| ## Overview | ||
|
|
||
| Settlement risk occurs when one party delivers an asset without receiving payment, or vice versa. This approach documents multiple mechanisms for achieving atomic settlement where both legs complete or neither does, eliminating counterparty risk. |
There was a problem hiding this comment.
Should distinguish:
- Single network atomicity, blockchain core property vs. tradfi
- Cross network trustless atomicity (L2<->L2) is not solved yet
|
The content of the approach doc is good, but it just lacks context about the core issue. |
Addressed Feedback (Round 2)@Meyanis95✅ ERC-7573 draft status - Added "(draft; requires trusted oracle)" in overview and "(draft)" notation in recommended components ✅ Single vs cross-network atomicity - Added dedicated paragraph distinguishing:
✅ Cross-network trust trade-off - Added explicit trade-off: "trustless cross-network DvP remains an unsolved problem" Ready for re-review. |
|
Looks great! |
Addresses reviewer feedback: - Promotes pattern to approach format (better fits comprehensive content) - Adds relationship clarification to ERC-7573 pattern - Adds persona TLDRs per approach template - Updates CHANGELOG and PRD references
oskarth
force-pushed
the
pr-009-dvp-atomic-settlement
branch
from
ecdae80 to
6c67b00
Compare
2 participants
What are you adding?
Description
Adds the Atomic DvP Settlement pattern documenting core payment locking and escrow mechanisms for delivery-versus-payment settlement:
patterns/pattern-delivery-vs-payment-atomic.mdChecklist