mirror of
https://github.com/bitcoin/bips.git
synced 2024-11-19 01:40:05 +01:00
- Fix Signature note formatting
- Change No EncryptedPayment Required title - Fix BIP70 link format in References
This commit is contained in:
parent
8e8c9778e9
commit
52b6cde023
@ -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
|
||||
|
||||
<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
|
||||
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]
|
||||
|
Loading…
Reference in New Issue
Block a user