mirror of
https://github.com/bitcoin/bips.git
synced 2025-03-03 18:57:18 +01:00
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.
This commit is contained in:
parent
85b5377777
commit
4081d3c57f
1 changed files with 1 additions and 1 deletions
|
@ -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:
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue