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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1Z5wPv-0004Hx-F1
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 13:33:11 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.43 as permitted sender)
client-ip=209.85.215.43; envelope-from=gavinandresen@gmail.com;
helo=mail-la0-f43.google.com;
Received: from mail-la0-f43.google.com ([209.85.215.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5wPt-0002kM-Cw
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 13:33:11 +0000
Received: by laka10 with SMTP id a10so74305637lak.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 06:33:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.43.110 with SMTP id v14mr17816791lal.4.1434720783046;
Fri, 19 Jun 2015 06:33:03 -0700 (PDT)
Received: by 10.25.90.75 with HTTP; Fri, 19 Jun 2015 06:33:03 -0700 (PDT)
In-Reply-To: <20150619103959.GA32315@savin.petertodd.org>
References: <20150619103959.GA32315@savin.petertodd.org>
Date: Fri, 19 Jun 2015 09:33:03 -0400
Message-ID: <CABsx9T1pnT=Tty3+tg+EUphLwQrWXf9EEwUOGuyNcdu=4wAqTg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=001a11c35152a01dfb0518def6a0
X-Spam-Score: 0.3 (/)
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
0.9 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z5wPt-0002kM-Cw
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
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: Fri, 19 Jun 2015 13:33:11 -0000
--001a11c35152a01dfb0518def6a0
Content-Type: text/plain; charset=UTF-8
I just sent the following email to F2Pool:
I was disappointed to see Peter Todd claiming that you have (or will?) run
his replace-by-fee patch.
I strongly encourage you to wait until most wallet software supports
replace-by-fee before doing that, because until that happens replace-by-fee
just makes it easier to steal from bitcoin-accepting merchants.
I will tell you the same thing about 8MB blocks: until most merchants
support bigger blocks I will strongly encourage you keep creating
less-than-1MB blocks. If we want Bitcoin to succeed more quickly, we should
all be thinking about what is good for the whole system: users, merchants,
exchanges and miners.
As always, if you have questions or concerns feel free to email me.
--
--
Gavin Andresen
--001a11c35152a01dfb0518def6a0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I just sent the following email to F2Pool:<div><br></div><=
div><br></div><div><span style=3D"font-size:12.8000001907349px">I was disap=
pointed to see Peter Todd claiming that you have (or will?) run his replace=
-by-fee patch.</span><div style=3D"font-size:12.8000001907349px"><br></div>=
<div style=3D"font-size:12.8000001907349px">I strongly encourage you to wai=
t until most wallet software supports replace-by-fee before doing that, bec=
ause until that happens replace-by-fee just makes it easier to steal from b=
itcoin-accepting merchants.</div><div style=3D"font-size:12.8000001907349px=
"><br></div><div style=3D"font-size:12.8000001907349px">I will tell you the=
same thing about 8MB blocks: until most merchants support bigger blocks I =
will strongly encourage you keep creating less-than-1MB blocks. If we want =
Bitcoin to succeed more quickly, we should all be thinking about what is go=
od for the whole system: users, merchants, exchanges and miners.</div><div =
style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12=
.8000001907349px">As always, if you have questions or concerns feel free to=
email me.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote"><br></div>-- <br><div class=3D"gmail_signature">--<br>Gavin Andresen<b=
r></div>
</div></div>
--001a11c35152a01dfb0518def6a0--
|
