From 05e9a86e332abf00d0e48a699838a0c2d319c152 Mon Sep 17 00:00:00 2001 From: Jack Grigg Date: Mon, 25 Jan 2021 11:11:03 +0000 Subject: [PATCH] ZIP 311: Minor edits from PR comments --- zip-0311.html | 4 ++-- zip-0311.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/zip-0311.html b/zip-0311.html index 3d8e4b40..2339ac14 100644 --- a/zip-0311.html +++ b/zip-0311.html @@ -22,7 +22,7 @@ Discussions-To: <https://g
  • A sender may need to prove that their payment was sent to a recipient, and available to be received (following the Zcash protocol in-band).
  • A third party may need to verify that a payment between a given sender and recipient was executed successfully.
    • -

    When a transaction involves only transparent addresses, proof-of-payment is simple: The sender provides the transaction ID, and the recipent examines the blockchain to confirm that the transaction was mined. A third party can also perform this verification if they know the transparent addresses of the involved parties.

    +

    When a transaction involves only transparent addresses, proof-of-payment is simple: The sender provides the transaction ID, and the recipient examines the blockchain to confirm that the transaction was mined. A third party can also perform this verification if they know the transparent addresses of the involved parties.

    However, if the transaction involves shielded addresses, the blockchain by itself does not contain enough information to allow a record of the payment to be reconstructed and verified:

    @@ -79,7 +79,7 @@ Discussions-To: <https://g

    Use cases

    Managing contributions for an event

    -

    Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally. Alice receives a single payment for half the amount, and wants proof of who it came from (so she knows which person to follow up with for the remaining amount). Carol can provide a payment disclosure that reveals:

    +

    Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally. Alice receives a single payment for half the amount, and wants proof of who it came from (so she knows which person to follow up with for the remaining amount). Carol can provide a payment disclosure that reveals to Alice:

    • The correct amount was sent to the Alice's recipient address in the given transaction.
    • Carol was the sender of that transaction (more precisely, Carol controls the spend authority used in that transaction).
      • diff --git a/zip-0311.rst b/zip-0311.rst index efd8b0d9..a291928b 100644 --- a/zip-0311.rst +++ b/zip-0311.rst @@ -27,7 +27,7 @@ There are various situations where a proof-of-payment may be desired. For exampl executed successfully. When a transaction involves only transparent addresses, proof-of-payment is simple: The -sender provides the transaction ID, and the recipent examines the blockchain to confirm +sender provides the transaction ID, and the recipient examines the blockchain to confirm that the transaction was mined. A third party can also perform this verification if they know the transparent addresses of the involved parties. @@ -61,7 +61,7 @@ Managing contributions for an event Alice runs an event on behalf of Bob and Carol, who both agree to split the cost equally. Alice receives a single payment for half the amount, and wants proof of who it came from (so she knows which person to follow up with for the remaining amount). Carol can provide -a payment disclosure that reveals: +a payment disclosure that reveals to Alice: - The correct amount was sent to the Alice's recipient address in the given transaction. - Carol was the sender of that transaction (more precisely, Carol controls the spend