MIME-Version: 1.0
In-Reply-To: <201511122025.24518.luke@dashjr.org>
References: <5644ECE6.9090304@mattcorallo.com>
	<201511122012.29966.luke@dashjr.org>
	<CAFzgq-xZA7VApQJv-b9n12H+GmL7u4Qv_481UsHWNqXGn6NubA@mail.gmail.com>
	<201511122025.24518.luke@dashjr.org>
Date: Thu, 12 Nov 2015 14:35:05 -0600
Message-ID: <CADvTj4r6JD=_0KHNcDPzEeDpUtdyCX2kHq2CnzbEqo8DBfwZjA@mail.gmail.com>
From: James Hilliard <james.hilliard1@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a113fc09ccc7aae05245de0e8
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Precedence: list

--001a113fc09ccc7aae05245de0e8
Content-Type: text/plain; charset=UTF-8

The priority space is causing major mempool bloating and GBT latency right
now since many of the free transactions aren't getting mined and cleared
out of the mempool anymore. From my testing setting minrelaytxfee=0.0001 is
not enough to prevent the mempool from getting large during a spam attack,
it is also necessary to set limitfreerelay=0 in order to prevent GBT
latency degradation. Without setting limitfreerelay=0 GBT degrades
significantly for every hour bitcoind is running.

On Thu, Nov 12, 2015 at 2:25 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Thursday, November 12, 2015 8:20:45 PM Chun Wang wrote:
> > The sort by priority part in the block is always the best place for spam
> > nowadays.
>
> What are you saying here? Spammers generally can't use the priority space
> at
> all, and it is a major way for legitimate users to get their transactions
> mined cheaply despite ongoing spam attempts. You're suggesting the exact
> opposite is true?? Please explain.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--001a113fc09ccc7aae05245de0e8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The priority space is causing major mempool bloating and G=
BT latency right now since many of the free transactions aren&#39;t getting=
 mined and cleared out of the mempool anymore. From my testing setting minr=
elaytxfee=3D0.0001 is not enough to prevent the mempool from getting large =
during a spam attack, it is also necessary to set limitfreerelay=3D0 in ord=
er to prevent GBT latency degradation. Without setting limitfreerelay=3D0 G=
BT degrades significantly for every hour bitcoind is running.<br></div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Nov 12, 2015 =
at 2:25 PM, Luke Dashjr via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@l=
ists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><span class=3D"">On Thursday, November 12, 2015 8:20:45 PM Chun Wang =
wrote:<br>
&gt; The sort by priority part in the block is always the best place for sp=
am<br>
&gt; nowadays.<br>
<br>
</span>What are you saying here? Spammers generally can&#39;t use the prior=
ity space at<br>
all, and it is a major way for legitimate users to get their transactions<b=
r>
mined cheaply despite ongoing spam attempts. You&#39;re suggesting the exac=
t<br>
opposite is true?? Please explain.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
Luke<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>

--001a113fc09ccc7aae05245de0e8--