From a81b43b49b09413961936f490afacec9df1106b5 Mon Sep 17 00:00:00 2001 From: jmacwhyte Date: Mon, 11 Jan 2016 15:22:06 -0800 Subject: [PATCH] added some details, fix typo --- 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 3d18e411..9fd4cb8b 100644 --- a/bip-invoicerequest-extension.mediawiki +++ b/bip-invoicerequest-extension.mediawiki @@ -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 * 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 +* 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. @@ -137,7 +138,7 @@ messages must set appropriate Content-Type headers as specified here: ====ReturnPaymentRequest==== 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: 
Content-Type: application/bitcoin-returnpaymentrequest
====Message or Communication Errors==== @@ -147,7 +148,7 @@ should be done through standard HTTP Status Code messaging ([https://tools.ietf. ===InvoiceRequest Message Creation=== * Create an InvoiceRequest message * 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 * Set notification_url to URL that the Receiver will submit completed ReturnPaymentRequest to * If NOT including certificate, set pki_type to "none"