Skip to content

Commit

Permalink
Fixed typo. Shortened title.
Browse files Browse the repository at this point in the history
  • Loading branch information
cfries committed Dec 11, 2023
1 parent cb62f5b commit d9338a6
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions ERCS/erc-7573.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
eip: 7573
title: Conditional-upon-Transfer-Decryption for Delivery-Versus-Payment
title: Conditional-upon-Transfer-Decryption for DvP
description: A Proposal for a Lean and Functional Delivery versus Payment
author: Christian Fries (@cfries), Peter Kohl-Landgraf (@pekola)
discussions-to: https://ethereum-magicians.org/t/erc-7573-conditional-upon-transfer-decryption-for-delivery-versus-payment/17232
Expand All @@ -24,7 +24,7 @@ that processes the (trigger-based) payment and emits the decrypted key depending
Within the domain of financial transactions and distributed ledger technology (DLT), the Hash-Linked Contract (HLC) concept has been recognized as valuable and has been thoroughly investigated.
The concept may help to solve the challenge of delivery-versus-payment (DvP), especially in cases where the asset chain and payment system (which may be a chain, too) are separated. The proposed solutions are based on an API-based interaction mechanism which bridges the communication between a so-called Asset Chain and a corresponding Payment System or require complex and problematic time-locks (\cite{BancaItalia}). We believe that an even more lightweight interaction across both systems is possible, especially when the payment system is also based on a DLT infrastructure.

## Specificaiton
## Specification

### Methods

Expand Down Expand Up @@ -64,14 +64,14 @@ The rationale is described in the following sequence diagram.

![image info](../assets/eip-7573/doc/DvP-Seq-Diag.png)

## Reference Implementation

A reference implementation is currently not provided. It may be added in a later phase.

## Test Cases

As there is no reference implementation, there are no test cases.

## Reference Implementation

A reference implementation is currently not provided. It may be added in a later phase.

## Security Considerations

No known security issues up to now.
Expand Down

0 comments on commit d9338a6

Please sign in to comment.