From 52b6cde023466771b2f3ae27ddd6ec9fb0738fcb Mon Sep 17 00:00:00 2001 From: Matt David Date: Sun, 21 Feb 2016 14:06:03 -0800 Subject: [PATCH] - Fix Signature note formatting - Change No EncryptedPayment Required title - Fix BIP70 link format in References --- bip-invoicerequest-extension.mediawiki | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/bip-invoicerequest-extension.mediawiki b/bip-invoicerequest-extension.mediawiki index 814845d5..dac70b35 100644 --- a/bip-invoicerequest-extension.mediawiki +++ b/bip-invoicerequest-extension.mediawiki @@ -350,6 +350,7 @@ Initial public key retrieval for InvoiceRequest encryption can be done in a numb * Sign the serialized EncryptedPaymentACK message with the Receiver's EC public key * Set signature to the result of the signature operation above + **SIGNATURE NOTE:** The EncryptedPayment message is signed with the ECDH-derived key as both the Sender and Receiver have the ECDH-derived key, however the EncryptedPaymentACK message is signed with the Receiver's EC key because only the Sender has access to it. This prevents both EncryptedPaymentACK spam and EncryptedPaymentACKs from being submitted by the Sender. @@ -390,7 +391,7 @@ EncryptedPayment and an EncryptedPaymentACK. In this case, the Receiver submits -===No EncryptedPayment Required=== +===EncryptedPayment NOT Required=== The following diagram shows a sample flow in which one mobile client is sending value to a second mobile client with the use of an InvoiceRequest, a Store & Forward server, and an EncryptedPaymentRequest (with require_payment_message = false). In this case, the Sender submits the transaction to the bitcoin network. @@ -406,7 +407,7 @@ In this case, the Sender submits the transaction to the bitcoin network. ==References== -* [bip-0070.mediawiki|BIP70 - Payment Protocol] +* [[bip-0070.mediawiki|BIP70 - Payment Protocol]] * [https://en.wikipedia.org/wiki/Elliptic_curve_Diffie–Hellman ECDH] * [http://csrc.nist.gov/publications/nistpubs/800-90A/SP800-90A.pdf HMAC_DRBG] * [https://tools.ietf.org/html/rfc6979 RFC6979]