diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2016-03-07 09:33:34 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2016-03-07 09:41:34 +0100 |
| commit | fa02af6e894a64e4c4abb9f4484aedc4b1f69904 (patch) | |
| tree | e349b226cff92f0ffd7273d2b0a36d461f6a9018 | |
| parent | b3a93c42016ba8d29f6f3cbb0cd23068b4bf1505 (diff) | |
bip 133: remove implementation detail
| -rw-r--r-- | bip-0133.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
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== |