summaryrefslogtreecommitdiff
path: root/b5/f3f7e4c25328bc2925506c8cb22acf3173877b
blob: c5cce791d71fb0b65f6868edd5c0f76b876e9f16 (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1USp2A-0005H2-02
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Apr 2013 13:37:54 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.178 as permitted sender)
	client-ip=74.125.82.178; envelope-from=gavinandresen@gmail.com;
	helo=mail-we0-f178.google.com; 
Received: from mail-we0-f178.google.com ([74.125.82.178])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1USp29-0004Sp-7T
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Apr 2013 13:37:53 +0000
Received: by mail-we0-f178.google.com with SMTP id z53so2263732wey.37
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 18 Apr 2013 06:37:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.109.197 with SMTP id hu5mr18469132wib.22.1366292266882; 
	Thu, 18 Apr 2013 06:37:46 -0700 (PDT)
Received: by 10.194.143.36 with HTTP; Thu, 18 Apr 2013 06:37:46 -0700 (PDT)
In-Reply-To: <CANEZrP0T7y8jqhMDUsf-HNw1sJnVuXngMa3x5+O5qgRE6eswew@mail.gmail.com>
References: <CANEZrP1yKeQMayFHsEUWtA3=q+v5rPAutjzEFVVHopPGNZ4jGQ@mail.gmail.com>
	<453bfc69-b2ab-4992-9807-55270fbda0db@email.android.com>
	<CANEZrP0z6W0ZDsytQ7Rcqb5L6rswn1wv8cbR7c383Dmpzu+gyg@mail.gmail.com>
	<CAPaL=UVJd3mdd0bs6Oo9vFHnv_6RbFowjmp0tD-ZbOzZxJEJ3g@mail.gmail.com>
	<CANEZrP3ocAJNoQ3xJqRTL8Gz3_T8xsCPPAvSfEOYpPo76wgbig@mail.gmail.com>
	<20130418090444.GA30995@savin>
	<CANEZrP0AYaWnVhrAbMXP0BGhb=CZMg_-PYVzwKbcCoRKC9V2rw@mail.gmail.com>
	<20130418100806.GA13908@savin>
	<CANEZrP0T7y8jqhMDUsf-HNw1sJnVuXngMa3x5+O5qgRE6eswew@mail.gmail.com>
Date: Thu, 18 Apr 2013 09:37:46 -0400
Message-ID: <CABsx9T18vvd1B4hSGU2eMnQTT9N-6Eoq29RAw_NiYdoNwe5uog@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=e89a8f2356f73a209b04daa2b568
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1USp29-0004Sp-7T
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Anti DoS for tx replacement
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 13:37:54 -0000

--e89a8f2356f73a209b04daa2b568
Content-Type: text/plain; charset=ISO-8859-1

> sure it's worth doing, at least immediately. Weakening the non-final ==
>>
> non-standard test to give a window of, say, 3 blocks, would be fine I
>> think.
>>
>
> Sure. I think Gavin wants some kind of wider memory pool limiter policy
> which would encompass such a thing already.
>

Yes.

I don't want to spend any time thinking about memory pool transaction
replacement until after we pay some technical debt:

+ Memory-limited memory pool, with relay policy matching block-creation
policy
+ Child-pays-for-parent fees
+ Auto-computed fees, based on transactions moving from the memory pool
into blocks


-- 
--
Gavin Andresen

--e89a8f2356f73a209b04daa2b568
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

=A0<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=
=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex">

<div><span style=3D"color:rgb(34,34,34)">sure it&#39;s worth doing, at leas=
t immediately. Weakening the non-final =3D=3D</span><br></div></blockquote>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">


non-standard test to give a window of, say, 3 blocks, would be fine I<br>
think.<br></blockquote><div><br></div></div><div>Sure. I think Gavin wants =
some kind of wider memory pool limiter policy which would encompass such a =
thing already.</div></div></div></div></blockquote><div><br></div><div>
Yes.</div><div><br></div><div>I don&#39;t want to spend any time thinking a=
bout memory pool transaction replacement until after we pay some technical =
debt:</div><div><br></div><div>+ Memory-limited memory pool, with relay pol=
icy matching block-creation policy</div>
<div>+ Child-pays-for-parent fees</div><div>+ Auto-computed fees, based on =
transactions moving from the memory pool into blocks</div></div><br clear=
=3D"all"><div><br></div>-- <br>--<br>Gavin Andresen<br>

--e89a8f2356f73a209b04daa2b568--