Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions bip-0121.mediawiki
Original file line number Diff line number Diff line change
Expand Up @@ -68,11 +68,11 @@ following table:
{|
| <tt>btcpop:</tt> URI parameter || <tt>bitcoin:</tt> URI parameter || BIP70 PaymentDetails data
|-
| <tt>label</tt> || <tt>label</tt> || <tt>merchant_data</tt>
| <tt>label</tt> || <tt>label</tt> || <tt>memo</tt>
|-
| <tt>amount</tt> || <tt>amount</tt> || <tt>sum of outputs.amount</tt>
|-
| <tt>message</tt> || <tt>message</tt> || <tt>memo</tt>
| <tt>message</tt> || <tt>message</tt> || <tt>-</tt>
|}

The <tt>txid</tt> parameter value must match the transaction hash of
Expand Down Expand Up @@ -104,9 +104,9 @@ not make their <tt>p</tt> parameter unnecessarily long.

Wallet implementations must support the <tt>http:</tt> and
<tt>https:</tt> schemes in which case <tt>POST</tt> method must be
used. The content type of the POST request must be set to

application/bitcoin-pop
used. The PoP is sent as a binary serialized transaction. The content
type of the POST request must be set to
<tt>application/bitcoin-pop</tt>

== Examples ==

Expand Down