mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2024-11-19 18:00:08 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #2 from jmacwhyte/proofread

Browse Source 
added some details, fix typo
This commit is contained in:
Matt David 2016-01-12 09:13:27 -08:00
commit 32e82105cb
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

@ -35,6 +35,7 @@ The motivation for this extension to BIP70 is twofold:
* Give the user the ability to decide who to release payment details to * Give the user the ability to decide who to release payment details to
* Allow an entity such as a political campaign to ensure donors match regulatory and legal requirements * Allow an entity such as a political campaign to ensure donors match regulatory and legal requirements
* Allow for an open standards based way to meet regulatory requirements * Allow for an open standards based way to meet regulatory requirements
* Automate the creation and maintenance of an "address book" of payees, without relying on static addresses or BIP32 X-Pubs which can become outdated and/or compromise privacy
In short we wanted to make bitcoin more human, while at the same time improving transaction privacy. In short we wanted to make bitcoin more human, while at the same time improving transaction privacy.
@ -137,7 +138,7 @@ messages must set appropriate Content-Type headers as specified here:
====ReturnPaymentRequest==== ====ReturnPaymentRequest====
Receiver must transmit ReturnPaymentRequest to Sender (or Sender's agent) via TLS-protected HTTP. Receiver transmitting Receiver must transmit ReturnPaymentRequest to Sender (or Sender's agent) via TLS-protected HTTP. Receiver transmitting
ReturnPaymentRequest messages must set appropritate Content-Type headers as specified here: ReturnPaymentRequest messages must set appropriate Content-Type headers as specified here:
<pre>Content-Type: application/bitcoin-returnpaymentrequest</pre> <pre>Content-Type: application/bitcoin-returnpaymentrequest</pre>
====Message or Communication Errors==== ====Message or Communication Errors====
@ -147,7 +148,7 @@ should be done through standard HTTP Status Code messaging ([https://tools.ietf.
===InvoiceRequest Message Creation=== ===InvoiceRequest Message Creation===
* Create an InvoiceRequest message * Create an InvoiceRequest message
* sender_public_key MUST be set to the public key of an EC keypair * sender_public_key MUST be set to the public key of an EC keypair
* nonce MUST be set to the current epoch time in microseconds * nonce MUST be set to a non-repeating number. The current epoch time in microseconds SHOULD be used, unless the creating device doesn't have access to a RTC (in the case of a smart card, for example)
* Amount is optional * Amount is optional
* Set notification_url to URL that the Receiver will submit completed ReturnPaymentRequest to * Set notification_url to URL that the Receiver will submit completed ReturnPaymentRequest to
* If NOT including certificate, set pki_type to "none" * If NOT including certificate, set pki_type to "none"