From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Alex Morcos <morcos@gmail•com>
Subject: Re: [bitcoin-dev] [BIP Proposal] New "feefilter" p2p message
Date: Wed, 17 Feb 2016 00:46:16 +0000 [thread overview]
Message-ID: <201602170046.17166.luke@dashjr.org> (raw)
In-Reply-To: <CAPWm=eXi98cC0KP=5WayU05hezDFswrPe+vA58cTHvVLc80OzQ@mail.gmail.com>
On Tuesday, February 16, 2016 8:20:26 PM Alex Morcos via bitcoin-dev wrote:
> # The feefilter message is defined as a message containing an int64_t where
> pchCommand == "feefilter"
What happened to extensibility? And why waste 64 bits for what is almost
certainly a small number?
> # The fee filter is additive with a bloom filter for transactions so if an
> SPV client were to load a bloom filter and send a feefilter message,
> transactions would only be relayed if they passed both filters.
This seems to make feefilter entirely useless for wallets?
Luke
next prev parent reply other threads:[~2016-02-17 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 20:20 Alex Morcos
2016-02-17 0:46 ` Luke Dashjr [this message]
2016-02-17 2:28 ` Alex Morcos
2016-02-17 2:36 ` Luke Dashjr
2016-02-17 2:43 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201602170046.17166.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=morcos@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox