summaryrefslogtreecommitdiff
path: root/3c/31c4bef7907579ee2a48db040199d12afe3961
blob: 70c88e8610d33fa72f3fc1458a1f0c48a85b863d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
Return-Path: <james.hilliard1@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 0F9C1955
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 12 Nov 2015 20:35:08 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com
	[209.85.215.48])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5E8C0FB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 12 Nov 2015 20:35:07 +0000 (UTC)
Received: by lffz63 with SMTP id z63so41289336lff.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 12 Nov 2015 12:35:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=74o9/8etsKjSGwHD6ZjtZRY0DoCVJT+GmU2ntRXdA5c=;
	b=KyYFlNu85Ix7l/iiTP5xg0ANQdDmBrCbHvLSjKwTURzREuGBuU5Jc9QgZMnb9D3Rpw
	LRbk0XmEdovhQsXrR5d6E3trjWrvUdUptkJyBD8+1ySvQAJbE1FsJNvJoJkvRrN2+nDk
	uEP5p8DUjlkDwsdlNvgL+n/iakZ998WoS+iVby6Mw078lXYc23Z1WqagLV9VGJ0mYFIe
	OgwMQiGk2U7Ghh8Sw8a3nRv3b2lUD0yL1Pg1ST84I0vv0EKqEwmedKHVuBddYs+WdKvA
	GIxnC+vYdSppad3+mhlkwj9u5E/MLS5neX/zRFV+R3Qm1vnrAVxJm+Nca50sSvPSuZ+K
	EUSA==
MIME-Version: 1.0
X-Received: by 10.25.3.207 with SMTP id 198mr7970571lfd.47.1447360505606; Thu,
	12 Nov 2015 12:35:05 -0800 (PST)
Received: by 10.112.183.169 with HTTP; Thu, 12 Nov 2015 12:35:05 -0800 (PST)
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
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
	HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 12 Nov 2015 20:42:55 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 20:35:08 -0000

--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--