bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

- Fix Signature note formatting

Browse Source 
- Change No EncryptedPayment Required title
- Fix BIP70 link format in References
This commit is contained in:
Matt David 2016-02-21 14:06:03 -08:00
parent 8e8c9778e9
commit 52b6cde023
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
bip-invoicerequest-extension.mediawiki
View File

@ -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 * Sign the serialized EncryptedPaymentACK message with the Receiver's EC public key
* Set signature to the result of the signature operation above * 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 **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 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. 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
<img src="bip-ir/mobile-sf-ir-with-payment.png"></img> <img src="bip-ir/mobile-sf-ir-with-payment.png"></img>
===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 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). 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. 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== ==References==
* [bip-0070.mediawiki|BIP70 - Payment Protocol] * [[bip-0070.mediawiki|BIP70 - Payment Protocol]]
* [https://en.wikipedia.org/wiki/Elliptic_curve_Diffie–Hellman ECDH] * [https://en.wikipedia.org/wiki/Elliptic_curve_Diffie–Hellman ECDH]
* [http://csrc.nist.gov/publications/nistpubs/800-90A/SP800-90A.pdf HMAC_DRBG] * [http://csrc.nist.gov/publications/nistpubs/800-90A/SP800-90A.pdf HMAC_DRBG]
* [https://tools.ietf.org/html/rfc6979 RFC6979] * [https://tools.ietf.org/html/rfc6979 RFC6979]