diff options
Diffstat (limited to 'bip-0070.mediawiki')
| -rw-r--r-- | bip-0070.mediawiki | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/bip-0070.mediawiki b/bip-0070.mediawiki index 699ff32..accd12b 100644 --- a/bip-0070.mediawiki +++ b/bip-0070.mediawiki @@ -86,9 +86,9 @@ about the merchant and a digital signature. |- | outputs || one or more outputs where Bitcoins are to be sent. If the sum of outputs.amount is zero, the customer will be asked how much to pay, and the bitcoin client may choose any or all of the Outputs (if there are more than one) for payment. If the sum of outputs.amount is non-zero, then the customer will be asked to pay the sum, and the payment shall be split among the Outputs with non-zero amounts (if there are more than one; Outputs with zero amounts shall be ignored). |- -| time || Unix timestamp (seconds since 1-Jan-1970) when the PaymentRequest was created. +| time || Unix timestamp (seconds since 1-Jan-1970 UTC) when the PaymentRequest was created. |- -| expires || Unix timestamp after which the PaymentRequest should be considered invalid. +| expires || Unix timestamp (UTC) after which the PaymentRequest should be considered invalid. |- | memo || UTF-8 encoded, plain-text (no formatting) note that should be displayed to the customer, explaining what this PaymentRequest is for. |- @@ -112,7 +112,7 @@ A PaymentRequest is PaymentDetails optionally tied to a merchant's identity: |- | pki_type || public-key infrastructure (PKI) system being used to identify the merchant. All implementation should support "none", "x509+sha256" and "x509+sha1". |- -| pki_data || PKI-system data that identifies the merchant and can be used to create a digital signature. In the case of X.509 certificates, pki_data one or more X.509 certificates (see Certificates section below). +| pki_data || PKI-system data that identifies the merchant and can be used to create a digital signature. In the case of X.509 certificates, pki_data contains one or more X.509 certificates (see Certificates section below). |- | serialized_payment_details || A protocol-buffer serialized PaymentDetails message. |- @@ -121,7 +121,7 @@ A PaymentRequest is PaymentDetails optionally tied to a merchant's identity: When a Bitcoin wallet application receives a PaymentRequest, it must authorize payment by doing the following: # Validate the merchant's identity and signature using the PKI system, if the pki_type is not "none". -# Validate that the time on the customer's system is before PaymentDetails.expires. If it is not, then the payment request must be rejected. +# Validate that customer's system unix time (UTC) is before PaymentDetails.expires. If it is not, then the payment request must be rejected. # Display the merchant's identity and ask the customer if they would like to submit payment (e.g. display the "Common Name" in the first X.509 certificate). PaymentRequest messages larger than 50,000 bytes should be rejected by @@ -212,7 +212,7 @@ chain: repeated bytes certificate = 1; } </pre> -If pki_type is "x509+sha256", then the Payment message is hashed using +If pki_type is "x509+sha256", then the PaymentRequest message is hashed using the SHA256 algorithm to produce the message digest that is signed. If pki_type is "x509+sha1", then the SHA1 algorithm is used. |