highperfocused/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-26 01:31:51 +01:00
Code Issues Packages Projects Releases Wiki Activity

Extended BIP70 fields, added BIP number

Browse Source
This commit is contained in:
jmacwhyte 2016-03-09 18:25:02 -08:00
parent f753dd7372
commit dddcb735f8
3 changed files with 22 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.mediawiki
View File

@ -302,6 +302,12 @@ Those proposing changes should consider that ultimately consent may rest with th
| Standard
| Draft
|-
| [[bip-0075.mediawiki|75]]
| Out of Band Address Exchange using Payment Protocol Encryption
| Justin Newton, Matt David, Aaron Voisine and James MacWhyte
| Standard
| Draft
|-
| [[bip-0099.mediawiki|99]]
| Motivation and deployment of consensus rule changes
| Jorge Timón

8
bip-0070/extensions.mediawiki
View File

@ -3,9 +3,11 @@
Add your extension below using tags starting at 1000 and submit a pull-req.
{|
| Field Number || Extension Name || Field Name || Payment Details Version || Description
| Field Number || Extension Name || Field Name || Description
|-
| 1000 || [[https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki|BIP0075]] || subtract_fee || 1 || If "true," indicates the sender can subtract the transaction fee from the requested amount. Otherwise, the transaction fee must be included separately from the requested amount.
| 1000 || [[https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki|BIP0075]] || subtractable_fee || If present, this field indicates how many Satoshis can be subtracted from the requested amount and instead applied towards the fee.
|-
| 1001 || [[https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki|BIP0075]] || replace_by_fee || 2 || If "true," indicates the sender can enable the Replace By Fee flag for this transaction and the receiver will still consider it accepted with zero confirmations. Otherwise, RBF transactions will not be accepted by the receiver until they are confirmed.
| 1001 || [[https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki|BIP0075]] || fee_per_kb || This field allows the receiver (merchant) to specify the minimum transaction fee that must be included with the transaction in order for it to be accepted with zero confirmations.
|-
| 1002 || [[https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki|BIP0075]] ||replace_by_fee || If "true," indicates the sender can enable the Replace By Fee flag for this transaction and the receiver will still consider it accepted with zero confirmations. Otherwise, RBF transactions will not be accepted by the receiver until they are confirmed.
|}

34
bip-0075.mediawiki
View File

@ -1,6 +1,6 @@
<pre>
BIP: 75
Title: Out of Band Address Exchange using Encrypted PaymentRequests
Title: Out of Band Address Exchange using Payment Protocol Encryption
Authors: Justin Newton <justin@netki.com>
Matt David <mgd@mgddev.com>
Aaron Voisine <voisine@gmail.com>
@ -464,37 +464,25 @@ In this case, the Sender submits the transaction to the bitcoin network.
==Extending BIP70 PaymentDetails==
To keep up with recent advancements in transaction type, two optional fields will be added to the BIP 70 PaymentDetails message. subtract_fee will be added to the current version 1 fields, making the complete list look like the following:
To keep up with recent advancements in transaction type and common use cases, three version 1 fields will be added to the BIP 70 PaymentDetails message, as described in the BIP 70 section titled [[bip-0070.mediawiki#extensibility|Extensibilit]]y:
<pre>
message PaymentDetails {
optional string network = 1 [default = "main"];
repeated Output outputs = 2;
required uint64 time = 3;
optional uint64 expires = 4;
optional string memo = 5;
optional string payment_url = 6;
optional bytes merchant_data = 7;
optional bool subtract_fee = 1000;
...
optional uint64 subtractable_fee = 1000;
optional uint64 fee_per_kb = 1001;
optional bool replace_by_fee = 1002;
}
</pre>
<b>replace_by_fee</b> will be added as a version 2 field. It is only available if payment_details_version is set to 2 or higher in the PaymentRequest message:
<pre>
// PaymentDetails v2
message PaymentDetails {
...
optional bool replace_by_fee = 1001;
}
</pre>
{| class="wikitable"
! Field Name !! Field Number || Payment Details Version !! Description
! Field Name !! Field Number !! Description
|-
| subtract_fee || 1000 || 1 || If "true," indicates the sender can subtract the transaction fee from the requested amount. Otherwise, the transaction fee must be included separately from the requested amount.
| subtractable_fee || 1000 || In some situations the receiver may be willing to cover the cost of the transaction fee. If present, this field indicates how many Satoshis can be subtracted from the requested amount and instead applied towards the fee.
|-
| replace_by_fee || 1001 || 2 || If "true," indicates the sender can enable the Replace By Fee flag for this transaction and the receiver will still consider it accepted with zero confirmations. Otherwise, RBF transactions will not be accepted by the receiver until they are confirmed.
| fee_per_kb || 1001 || This field allows the receiver (merchant) to specify the minimum transaction fee that must be included with the transaction in order for it to be accepted with zero confirmations.
|-
| replace_by_fee || 1002 || If "true," indicates the sender can enable the Replace By Fee flag for this transaction and the receiver will still consider it accepted with zero confirmations. Otherwise, RBF transactions will not be accepted by the receiver until they are confirmed.
|}
==References==