Removed BIP70 extensions

1 files changed, 0 insertions, 23 deletions

diff --git a/bip-0075.mediawiki b/bip-0075.mediawiki
index 3075dd3..d0793be 100644
--- a/bip-0075.mediawiki
+++ b/bip-0075.mediawiki
@@ -444,29 +444,6 @@ The following diagram shows a sample flow in which one mobile client is sending
 
 <img src="bip-0075/mobile-sf-encrypted-ir-without-payment.png" alt="EncryptedInvoiceRequest without payment">
 
-==Extending BIP70 PaymentDetails==
-
-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 uint64 subtractable_fee = 1000;
-        optional uint64 fee_per_kb = 1001;
-        optional bool replace_by_fee = 1002;
-}
-</pre>
-
-{| class="wikitable"
-! Field Name !! Field Number !! Description
-|-
-| 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.
-|-
-| 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==
 
 * [[bip-0070.mediawiki|BIP70 - Payment Protocol]]