From b3a93c42016ba8d29f6f3cbb0cd23068b4bf1505 Mon Sep 17 00:00:00 2001
From: MarcoFalke <falke.marco@gmail.com>
Date: Sun, 6 Mar 2016 18:18:23 +0100
Subject: Update bip-0133.mediawiki

---
 bip-0133.mediawiki | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'bip-0133.mediawiki')

diff --git a/bip-0133.mediawiki b/bip-0133.mediawiki
index b5146e3..f78f328 100644
--- a/bip-0133.mediawiki
+++ b/bip-0133.mediawiki
@@ -28,13 +28,13 @@ After receiving a feefilter message, a node can know before sending an inv that
 # Feature discovery is enabled by checking protocol version >= 70013
 
 ==Considerations==
-The propagation efficiency of transactions across the network should not be adversely affected by this change. In general, transactions which are not accepted to your mempool are not relayed and the funcionality implemented with this message is meant only to filter those transactions.  There could be a small number of edge cases where a node's mempool min fee is actually less than the filter value a peer is aware of and transactions with fee rates between these values will now be newly inhibited.
+The propagation efficiency of transactions across the network should not be adversely affected by this change. In general, transactions which are not accepted to a node's mempool are not relayed by this node and the functionality implemented with this message is meant only to filter those transactions. There could be a small number of edge cases where a node's mempool min fee is actually less than the filter value a peer is aware of and transactions with fee rates between these values will now be newly inhibited.
 
 Feefilter messages are not sent to whitelisted peers if the "-whitelistforcerelay" option is set. In that case, transactions are intended to be relayed even if they are not accepted to the mempool.
 
-There are privacy concerns with deanonymizing a node by the fact that it is broadcasting identifying information about its mempool min fee. To help ameliorate this concern, the implementaion quantizes the filter value broadcast with a small amount of randomness, in addition, the messages are broadcast to different peers at individually randomly distributed times.
+There are privacy concerns with deanonymizing a node by the fact that it is broadcasting identifying information about its mempool min fee. To help ameliorate this concern, the implementation quantizes the filter value broadcast with a small amount of randomness, in addition, the messages are broadcast to different peers at individually randomly distributed times.
 
-If a node is using prioritisetransaction to accept transactions whose actual fee rates might fall below the node's mempool min fee, it may want to consider setting "-nofeefilter" to make sure it is exposed to all possible txid's.
+If a node is using prioritisetransaction to accept transactions whose actual fee rates might fall below the node's mempool min fee, it may want to consider setting "-feefilter=0" to make sure it is exposed to all possible txid's.
 
 ==Backward compatibility==
 
-- 
cgit v1.2.3


From fa02af6e894a64e4c4abb9f4484aedc4b1f69904 Mon Sep 17 00:00:00 2001
From: MarcoFalke <falke.marco@gmail.com>
Date: Mon, 7 Mar 2016 09:33:34 +0100
Subject: bip 133: remove implementation detail

---
 bip-0133.mediawiki | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'bip-0133.mediawiki')

diff --git a/bip-0133.mediawiki b/bip-0133.mediawiki
index f78f328..7d98f87 100644
--- a/bip-0133.mediawiki
+++ b/bip-0133.mediawiki
@@ -34,11 +34,11 @@ Feefilter messages are not sent to whitelisted peers if the "-whitelistforcerela
 
 There are privacy concerns with deanonymizing a node by the fact that it is broadcasting identifying information about its mempool min fee. To help ameliorate this concern, the implementation quantizes the filter value broadcast with a small amount of randomness, in addition, the messages are broadcast to different peers at individually randomly distributed times.
 
-If a node is using prioritisetransaction to accept transactions whose actual fee rates might fall below the node's mempool min fee, it may want to consider setting "-feefilter=0" to make sure it is exposed to all possible txid's.
+If a node is using prioritisetransaction to accept transactions whose actual fee rates might fall below the node's mempool min fee, it may want to consider disabling the fee filter to make sure it is exposed to all possible txid's.
 
 ==Backward compatibility==
 
-Older clients remain fully compatible and interoperable after this change.  The sending of feefilter messages can be disabled by unsetting the "-feefilter" option.
+Older clients remain fully compatible and interoperable after this change. Also, clients implementing this BIP can choose to not send any feefilter messages.
 
 ==Implementation==
 
-- 
cgit v1.2.3

