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
134
135
136
137
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Z4bPZ-0006HH-Fq
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 20:55:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.171 as permitted sender)
client-ip=209.85.212.171; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f171.google.com;
Received: from mail-wi0-f171.google.com ([209.85.212.171])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4bPV-0003ho-BG
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 20:55:17 +0000
Received: by wifx6 with SMTP id x6so433909wif.0
for <bitcoin-development@lists.sourceforge.net>;
Mon, 15 Jun 2015 13:55:07 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.104.197 with SMTP id gg5mr35408494wib.27.1434401707271;
Mon, 15 Jun 2015 13:55:07 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.28.14.196 with HTTP; Mon, 15 Jun 2015 13:55:07 -0700 (PDT)
In-Reply-To: <CALqxMTFC7zBN9GvHAZLQj4SbXjzkCAM9meSErd3qn7uCoON98Q@mail.gmail.com>
References: <CALqxMTGBt7MNs5YWf8QzKe+4Fr-uKVimf8=VbytBANEDm=s50g@mail.gmail.com>
<CANEZrP31AEson9DZ=ZU7d4t=DvmGodh1ja6EaZ6xQZ3bFEXeVA@mail.gmail.com>
<CALqxMTFC7zBN9GvHAZLQj4SbXjzkCAM9meSErd3qn7uCoON98Q@mail.gmail.com>
Date: Mon, 15 Jun 2015 22:55:07 +0200
X-Google-Sender-Auth: pCpmaifW53XeryuEPqoElLb2eRg
Message-ID: <CANEZrP148U0V7bU-u0tOTk2xWwq5wy-yU-jk805DcU_3cBHtnw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Adam Back <adam@cypherspace.org>
Content-Type: multipart/alternative; boundary=f46d041825bc3a2d54051894ac9b
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1Z4bPV-0003ho-BG
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] questions about bitcoin-XT code fork &
non-consensus hard-fork
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: Mon, 15 Jun 2015 20:55:17 -0000
--f46d041825bc3a2d54051894ac9b
Content-Type: text/plain; charset=UTF-8
Hi Adam,
I replied publicly because your questions were sent to the mailing list.
I'd have been happy to reply in private if so asked.
I started to write up a much longer reply, but I'm tired - we've long since
been going in circles. I feel like I've written down answers to almost all
your questions before, including some in the email above.
Still, there are a few new ones. Let me work through them now.
Yes, I am on the bitcoin-security list. I have always been on it. I have
taken part in many threads there and started one or two myself. I guess
you're not though, otherwise you'd know that. You can ask, I'm sure Gavin
will add you if you like.
Re: BIP. Gavin is working on a BIP to go along with his patch. I hope that
will satisfy. I do not expect the resulting discussion to differ much from
the discussion so far, though.
Re: summit. No, I would not attend. I have been to several Bitcoin
conferences over the years where the block size issue was discussed. No
progress was ever made at these events.
Re: if some flaw or bug was found in the patch. Yes, of course if there was
some specific problem with the code then we would fix it. There will be
time to review Gavin's patches for these reasons.
Re: anyone who agrees with noted non-programmers Mike&Gavin must be
non-technical, stupid, uninformed, etc .... OK, go ahead and show them the
error of their ways. Anyone can write blogs.
--f46d041825bc3a2d54051894ac9b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Adam,<div><br></div><div>I replied publicly because you=
r questions were sent to the mailing list. I'd have been happy to reply=
in private if so asked.</div><div><br></div><div>I started to write up a m=
uch longer reply, but I'm tired - we've long since been going in ci=
rcles. I feel like I've written down answers to almost all your questio=
ns before, including some in the email above.</div><div><br></div><div>Stil=
l, there are a few new ones. Let me work through them now.</div><div><br></=
div><div><br></div><div>Yes, I am on the bitcoin-security list. I have alwa=
ys been on it. I have taken part in many threads there and started one or t=
wo myself. I guess you're not though, otherwise you'd know that. Yo=
u can ask, I'm sure Gavin will add you if you like.</div><div><br></div=
><div><br></div><div><div>Re: BIP. Gavin is working on a BIP to go along wi=
th his patch. I hope that will satisfy. I do not expect the resulting discu=
ssion to differ much from the discussion so far, though.</div></div><div><b=
r></div><div><br></div><div>Re: summit. No, I would not attend. I have been=
to several Bitcoin conferences over the years where the block size issue w=
as discussed. No progress was ever made at these events.</div><div><br></di=
v><div><br></div><div><br></div><div>Re: if some flaw or bug was found in t=
he patch. Yes, of course if there was some specific problem with the code t=
hen we would fix it. There will be time to review Gavin's patches for t=
hese reasons.</div><div><br></div><div><br></div><div><br></div><div>Re: an=
yone who agrees with noted non-programmers Mike&Gavin must be non-techn=
ical, stupid, uninformed, etc .... OK, go ahead and show them the error of =
their ways. Anyone can write blogs.</div><div><span style=3D"font-size:12.8=
000001907349px"><br></span></div><div><br></div><div><br></div></div>
--f46d041825bc3a2d54051894ac9b--
|
