From 4081d3c57f999bf80fd2fdb6b76235997d611cbe Mon Sep 17 00:00:00 2001
From: "David A. Harding" <dave@dtrt.org>
Date: Mon, 31 Mar 2014 21:34:07 -0400
Subject: Update bip-0070.mediawiki

Slightly re-worded description of the signature field in PaymentRequest

The previous phrasing confused me and I had to check the Bitcoin Core source code to see what it was expecting for a signature.
---
 bip-0070.mediawiki | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'bip-0070.mediawiki')

diff --git a/bip-0070.mediawiki b/bip-0070.mediawiki
index 4461118..3988839 100644
--- a/bip-0070.mediawiki
+++ b/bip-0070.mediawiki
@@ -118,7 +118,7 @@ A PaymentRequest is PaymentDetails optionally tied to a merchant's identity:
 |-
 | serialized_payment_details || A protocol-buffer serialized PaymentDetails message.
 |-
-| signature || digital signature over a hash of the protocol buffer serialized variation of the PaymentRequest message, where signature is a zero-byte array and fields are serialized in numerical order (all current protocol buffer implementations serialize fields in numerical order), using the public key in pki_data.
+| signature || digital signature over a hash of the protocol buffer serialized variation of the PaymentRequest message, with all fields serialized in numerical order (all current protocol buffer implementations serialize fields in numerical order) and signed using the public key in pki_data.  Before serialization, the signature field must be set to a zero-byte placeholder.
 |}
 When a Bitcoin wallet application receives a PaymentRequest, it must authorize payment by doing the following:
 
-- 
cgit v1.2.3

