From 68c801d18b613f7745e6be3cbb7d8242ebe7b2b3 Mon Sep 17 00:00:00 2001
From: Derren Desouza <derrend@yahoo.co.uk>
Date: Fri, 12 Sep 2014 08:11:39 +1000
Subject: Update bip-0070.mediawiki

Clarification regarding the signature field in payment details and which key should be used for signing.
---
 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 03baf5b..c2f7725 100644
--- a/bip-0070.mediawiki
+++ b/bip-0070.mediawiki
@@ -126,7 +126,7 @@ A PaymentRequest is PaymentDetails optionally tied to a merchant's identity:
 |-
 | signature || digital signature over a hash of the protocol buffer serialized variation of the PaymentRequest message,
 with all serialized fields serialized in numerical order (all current protocol buffer implementations serialize
-fields in numerical order) and signed using the public key in pki_data. Optional fields that are not set
+fields in numerical order) and signed using the private key that corresponds to the public key in pki_data. Optional fields that are not set
 are not serialized (however, setting a field to its default value will cause it to be serialized and will affect
 the signature). Before serialization, the signature field must be set to an empty value so that the field is included in the signed PaymentRequest hash but contains no data.
 |}
-- 
cgit v1.2.3

