summaryrefslogtreecommitdiff
path: root/72/5f778690bcd9c9aa41c9e35e5fd262ec85eb87
blob: a9a0ef4cec1a1d03916bf967589bceafffcbf76e (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
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
Return-Path: <mark@friedenbach.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 95D13895
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Aug 2015 22:55:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com
	[209.85.223.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3D1D41B5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Aug 2015 22:55:18 +0000 (UTC)
Received: by iodb91 with SMTP id b91so116812085iod.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Aug 2015 15:55:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=wtDLflsjrqi+do9jCvgOaRl9Fkmi/91TC7Hax2Crj2M=;
	b=YrRrhnjjHssdh0mBy+50qDiXf1Noc5aJqA78npvli7nua7AzCMvje0OQKrK3mbzPUZ
	DsXb4Ch+7zIAoYUyeKCszN/YwTEXoY5+cXYE+finfVm6tp8fDfIVGJL3qx1/e2CnwQQi
	aE1vd/6Ot8DX3JTi3jHeg8Oo5UTnO1VAlxeB9RdJvxPj89fchqXEpzYA/JItbiJBFVcB
	ge6yt/DYjCBLrigDuVrU7T1chHy2RxU1oXh250wuic2A2wXFQ2VSS214QW2dIiq2VH2U
	03xZrbo+NcEqRcHxsspp7qfyvP7O+C91jtBAcWGTKlFQKILiAvfi3FBeADNR7fffb9sS
	y9pg==
X-Gm-Message-State: ALoCoQkx+TZHvDko14jHLjNE3UI4SrVlEzxk0aoFKriQPSmkBUg4EI1McDLizLFgttqeGLTBZjwL
MIME-Version: 1.0
X-Received: by 10.107.11.67 with SMTP id v64mr56328821ioi.105.1439679317672;
	Sat, 15 Aug 2015 15:55:17 -0700 (PDT)
Received: by 10.107.138.14 with HTTP; Sat, 15 Aug 2015 15:55:17 -0700 (PDT)
X-Originating-IP: [172.56.40.188]
Received: by 10.107.138.14 with HTTP; Sat, 15 Aug 2015 15:55:17 -0700 (PDT)
In-Reply-To: <CAKujSOGdXoo4DORHtD7KV1fgjHzvcSQnUr=yNL4ruKhn1Lwjig@mail.gmail.com>
References: <CA+w+GKT7t5OahS-+P=QAmOyFzPnOs4J6KSo+mhSrC0YggmMupg@mail.gmail.com>
	<E7866FD5-9CEC-400F-8270-407499E0B012@gmail.com>
	<CAKujSOFNHNngt0HV=B3YHxOwXksk+JZDaHt+mUVniwMPTM6SaA@mail.gmail.com>
	<CC1B6D0E-F9D5-422B-980D-C589CDC00612@gmail.com>
	<CAKujSOGdXoo4DORHtD7KV1fgjHzvcSQnUr=yNL4ruKhn1Lwjig@mail.gmail.com>
Date: Sat, 15 Aug 2015 15:55:17 -0700
Message-ID: <CAOG=w-vGoPuDBcDkdrLVEoE5Q_UzVR7FfThBT9QALgiSSHDsFg@mail.gmail.com>
From: Mark Friedenbach <mark@friedenbach.org>
To: Ken Friece <kfriece@gmail.com>
Content-Type: multipart/alternative; boundary=001a113f9694521c21051d61760e
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
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: Sat, 15 Aug 2015 22:55:20 -0000

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

I would like very much to know how it is that we're supposed to be making
money off of lightning, and therefore how it represents a conflict of
interest. Apparently there is tons of money to be made in releasing
open-source protocols! I would hate to miss out on that.

We are working on lightning because Mike of all people said, essentially, "
if you're so fond of micro payment channels, why aren't you working on
them?" And he was right! So we looked around and found the best proposal
and funded it.
On Aug 15, 2015 3:28 PM, "Ken Friece via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I know full well who works for Blockstream and I know you're not one of
> those folks. The Blockstream core devs are very vocal against a reasonabl=
e
> blocksize increase (17% growth per year in Pieter's BIP is not what I
> consider reasonable because it doesn't come close to keeping with
> technological increases). I think we can both agree that more on-chain
> space means less demand for lightning, and vice versa, which is a blatant
> conflict of interest.
>
> I'm also trying to figure out how things like lightning are not competing
> directly with miners for fees. More off-chain transactions means less
> blockchain demand, which would lower on-chain fees. I'm not sure what is
> controversial about that statement.
>
> The lightning network concept is actually a brilliant way to take fees
> away from miners without having to make any investment at all in SSH-256
> ASIC mining hardware.
>
> On Sat, Aug 15, 2015 at 6:16 PM, Eric Lombrozo <elombrozo@gmail.com>
> wrote:
>
>>
>> On Aug 15, 2015, at 3:01 PM, Ken Friece via bitcoin-dev <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> What are you so afraid of, Eric? If Mike's fork is successful, consensus
>> is reached around larger blocks. If it is rejected, the status quo will
>> remain for now. Network consensus, NOT CORE DEVELOPER CONSENSUS, is the
>> only thing that matters, and those that go against network consensus wil=
l
>> be severely punished with complete loss of income.
>>
>>
>> I fully agree that core developers are not the only people who should
>> have a say in this. But again, we=E2=80=99re not talking about merely fo=
rking some
>> open source project - we=E2=80=99re talking about forking a ledger repre=
senting
>> real assets that real people are holding=E2=80=A6and I think it=E2=80=99=
s fair to say that
>> the risk of permanent ledger forks far outweighs whatever benefits any
>> change in the protocol might bring. And this would be true even if there
>> were unanimous agreement that the change is good (which there clearly IS
>> NOT in this case) but the deployment mechanism could still break things.
>>
>> If anything we should attempt a hard fork with a less contentious change
>> first, just to test deployability.
>>
>> I'm not sure who appointed the core devs some sort of Bitcoin Gods that
>> can hold up any change that they happen to disagree with. It seems like =
the
>> core devs are scared to death that the bitcoin network may change withou=
t
>> their blessing, so they go on and on about how terrible hard forks are.
>> Hard forks are the only way to keep core devs in check.
>>
>>
>> Again, let=E2=80=99s figure out a hard fork mechanism and test it with a=
 far less
>> contentious change first
>>
>> Despite significant past technical bitcoin achievements, two of the most
>> vocal opponents to a reasonable blocksize increase work for a company
>> (Blockstream) that stands to profit directly from artificially limiting =
the
>> blocksize. The whole situation reeks. Because of such a blatant conflict=
 of
>> interest, the ethical thing to do would be for them to either resign fro=
m
>> Blockstream or immediately withdraw themselves from the blocksize debate=
.
>> This is the type of stuff that I hoped would end with Bitcoin, but alas,=
 I
>> guess human nature never changes.
>>
>>
>> For the record, I do not work for Blockstream. Neither do a bunch of
>> other people who have published a number of concerns. Very few of the
>> concerns I=E2=80=99ve seen from the technical community seem to be motiv=
ated
>> primarily by profit motives.
>>
>> It should also be pointed out that *not* making drastic changes is the
>> default consensus policy=E2=80=A6and the burden of justifying a change f=
alls on
>> those who want to make the change. Again, the risk of permanent ledger
>> forks far outweighs whatever benefits protocol changes might bring.
>>
>> Personally, I think miners should give Bitcoin XT a serious look. Miners
>> need to realize that they are in direct competition with the lightning
>> network and sidechains for fees. Miners, ask yourselves if you think you=
'll
>> earn more fees with 1 MB blocks and more off-chain transactions or with =
8
>> MB blocks and more on-chain transactions=E2=80=A6
>>
>>
>> Miners are NOT in direct competition with the lightning network and
>> sidechains - these claims are patently false. I recommend you take a loo=
k
>> at these ideas and understand them a little better before trying to make
>> any such claims. Again, I do not work for Blockstream=E2=80=A6and my age=
nda in this
>> post is not to promote either of these ideas=E2=80=A6but with all due re=
spect, I do
>> not think you properly understand them at all.
>>
>> The longer this debate drags on, the more I agree with BIP 100 and Jeff
>> Garzik because the core devs are already being influenced by outside for=
ces
>> and should not have complete control of the blocksize. It's also
>> interesting to note that most of the mining hashpower is already voting =
for
>> 8MB blocks BIP100 style.
>>
>>
>> I don=E2=80=99t think the concern here is so much that some people want =
to
>> increase block size. It=E2=80=99s the *way* in which this change is bein=
g pushed
>> that is deeply problematic.
>>
>> On Sat, Aug 15, 2015 at 5:32 PM, Eric Lombrozo via bitcoin-dev <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>>> You deeply disappoint me, Mike.
>>>
>>> Not only do you misrepresent many cogent, well thought out positions
>>> from a great number of people who have published and posted a number of
>>> articles detailing an explaining in-depth technical concerns=E2=80=A6yo=
u also seem
>>> to fancy yourself more capable of reading into the intentions of someon=
e
>>> who disappeared from the scene years ago, before we even were fully awa=
re
>>> of many things we now know that bring the original =E2=80=9Cplan=E2=80=
=9D into question.
>>>
>>> I ask of you, as a civilized human being, to stop doing this divisive
>>> crap. Despite your protestations to the contrary, YOU are the one who i=
s
>>> proposing a radical departure from the direction of the project. Also, =
as
>>> several of us have clearly stated before, equating the fork of an open
>>> source project with a fork of a cryptoledger is completely bogus - ther=
e=E2=80=99s
>>> a lot of other people=E2=80=99s money at stake. This isn=E2=80=99t a de=
mocracy - consensus
>>> is all or nothing. The fact that a good number of the people most
>>> intimately familiar with the inner workings of Satoshi=E2=80=99s invent=
ion do not
>>> believe doing this is a good idea should give you pause.
>>>
>>> Please stop using Bitcoin as your own political football=E2=80=A6for th=
e sake of
>>> Bitcoin=E2=80=A6and for your own sake. Despite your obvious technical a=
bilities
>>> (and I sincerely do believe you have them) you are discrediting yoursel=
f
>>> and hurting your own reputation.
>>>
>>>
>>> - Eric
>>>
>>> On Aug 15, 2015, at 10:02 AM, Mike Hearn via bitcoin-dev <
>>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>>
>>> Hello,
>>>
>>> As promised, we have released Bitcoin XT 0.11A which includes the bigge=
r
>>> blocks patch set. You can get it from
>>>
>>>      https://bitcoinxt.software/
>>>
>>> I feel sad that it's come to this, but there is no other way. The
>>> Bitcoin Core project has drifted so far from the principles myself and =
many
>>> others feel are important, that a fork is the only way to fix things.
>>>
>>> Forking is a natural thing in the open source community, Bitcoin is not
>>> the first and won't be the last project to go through this. Often in fo=
rks,
>>> people say there was insufficient communication. So to ensure everythin=
g is
>>> crystal clear I've written a blog post and a kind of "manifesto" to
>>> describe why this is happening and how XT plans to be different from Co=
re
>>> (assuming adoption, of course).
>>>
>>> The article is here:
>>>
>>>     https://medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1
>>>
>>> It makes no attempt to be neutral: this explains things from our point
>>> of view.
>>>
>>> The manifesto is on the website.
>>>
>>> I say to all developers on this list: if you also feel that Core is no
>>> longer serving the interests of Bitcoin users, come join us. We don't b=
ite.
>>>
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

<p dir=3D"ltr">I would like very much to know how it is that we&#39;re supp=
osed to be making money off of lightning, and therefore how it represents a=
 conflict of interest. Apparently there is tons of money to be made in rele=
asing open-source protocols! I would hate to miss out on that.</p>
<p dir=3D"ltr">We are working on lightning because Mike of all people said,=
 essentially, &quot; if you&#39;re so fond of micro payment channels, why a=
ren&#39;t you working on them?&quot; And he was right! So we looked around =
and found the best proposal and funded it.</p>
<div class=3D"gmail_quote">On Aug 15, 2015 3:28 PM, &quot;Ken Friece via bi=
tcoin-dev&quot; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org=
">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br type=3D"attributi=
on"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>I know full w=
ell who works for Blockstream and I know you&#39;re not one of those folks.=
 The Blockstream core devs are very vocal against a reasonable blocksize in=
crease (17% growth per year in Pieter&#39;s BIP is not what I consider reas=
onable because it doesn&#39;t come close to keeping with technological incr=
eases). I think we can both agree that more on-chain space means less deman=
d for lightning, and vice versa, which is a blatant conflict of interest.<b=
r><br></div>I&#39;m also trying to figure out how things like lightning are=
 not competing directly with miners for fees. More off-chain transactions m=
eans less blockchain demand, which would lower on-chain fees. I&#39;m not s=
ure what is controversial about that statement.<br><br></div><div>The light=
ning network concept is actually a brilliant way to take fees away from min=
ers without having to make any investment at all in SSH-256 ASIC mining har=
dware.<br></div><div><div><div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Sat, Aug 15, 2015 at 6:16 PM, Eric Lombrozo <span dir=3D"l=
tr">&lt;<a href=3D"mailto:elombrozo@gmail.com" target=3D"_blank">elombrozo@=
gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div sty=
le=3D"word-wrap:break-word"><br><div><blockquote type=3D"cite"><div>On Aug =
15, 2015, at 3:01 PM, Ken Friece via bitcoin-dev &lt;<a href=3D"mailto:bitc=
oin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linu=
xfoundation.org</a>&gt; wrote:</div><br><div><div dir=3D"ltr"><div><div>Wha=
t are you so afraid of, Eric? If Mike&#39;s fork is successful, consensus i=
s reached around larger blocks. If it is rejected, the status quo will rema=
in for now. Network consensus, NOT CORE DEVELOPER CONSENSUS, is the only th=
ing that matters, and those that go against network consensus will be sever=
ely punished with complete loss of income.<br></div></div></div></div></blo=
ckquote><div><br></div>I fully agree that core developers are not the only =
people who should have a say in this. But again, we=E2=80=99re not talking =
about merely forking some open source project - we=E2=80=99re talking about=
 forking a ledger representing real assets that real people are holding=E2=
=80=A6and I think it=E2=80=99s fair to say that the risk of permanent ledge=
r forks far outweighs whatever benefits any change in the protocol might br=
ing. And this would be true even if there were unanimous agreement that the=
 change is good (which there clearly IS NOT in this case) but the deploymen=
t mechanism could still break things.</div><div><br></div><div>If anything =
we should attempt a hard fork with a less contentious change first, just to=
 test deployability.</div><div><div><br></div><blockquote type=3D"cite"><di=
v><div dir=3D"ltr"><div><div>I&#39;m not sure who appointed the core devs s=
ome sort of Bitcoin Gods that can hold up any change that they happen to di=
sagree with. It seems like the core devs are scared to death that the bitco=
in network may change without their blessing, so they go on and on about ho=
w terrible hard forks are. Hard forks are the only way to keep core devs in=
 check.</div></div></div></div></blockquote><div><br></div><div>Again, let=
=E2=80=99s figure out a hard fork mechanism and test it with a far less con=
tentious change first</div><br><blockquote type=3D"cite"><div><div dir=3D"l=
tr"><div>Despite significant past technical bitcoin achievements, two of th=
e most vocal opponents to a reasonable blocksize increase work for a compan=
y (Blockstream) that stands to profit directly from artificially limiting t=
he blocksize. The whole situation reeks. Because of such a blatant conflict=
 of interest, the ethical thing to do would be for them to either resign fr=
om Blockstream or immediately withdraw themselves from the blocksize debate=
. This is the type of stuff that I hoped would end with Bitcoin, but alas, =
I guess human nature never changes.<br></div></div></div></blockquote><div>=
<br></div><div>For the record, I do not work for Blockstream. Neither do a =
bunch of other people who have published a number of concerns. Very few of =
the concerns I=E2=80=99ve seen from the technical community seem to be moti=
vated primarily by profit motives.</div><div><br></div><div>It should also =
be pointed out that *not* making drastic changes is the default consensus p=
olicy=E2=80=A6and the burden of justifying a change falls on those who want=
 to make the change. Again, the risk of permanent ledger forks far outweigh=
s whatever benefits protocol changes might bring.</div><br><blockquote type=
=3D"cite"><div><div dir=3D"ltr"><div>Personally, I think miners should give=
 Bitcoin XT a serious look. Miners need to realize that they are in direct =
competition with the lightning network and sidechains for fees. Miners, ask=
 yourselves if you think you&#39;ll earn more fees with 1 MB blocks and mor=
e off-chain transactions or with 8 MB blocks and more on-chain transactions=
=E2=80=A6<br></div></div></div></blockquote><div><br></div>Miners are NOT i=
n direct competition with the lightning network and sidechains - these clai=
ms are patently false. I recommend you take a look at these ideas and under=
stand them a little better before trying to make any such claims. Again, I =
do not work for Blockstream=E2=80=A6and my agenda in this post is not to pr=
omote either of these ideas=E2=80=A6but with all due respect, I do not thin=
k you properly understand them at all.<br><br><blockquote type=3D"cite"><di=
v><div dir=3D"ltr"><div>The longer this debate drags on, the more I agree w=
ith BIP 100 and Jeff Garzik because the core devs are already being influen=
ced by outside forces and should not have complete control of the blocksize=
. It&#39;s also interesting to note that most of the mining hashpower is al=
ready voting for 8MB blocks BIP100 style. =C2=A0</div></div></div></blockqu=
ote><div><br></div>I don=E2=80=99t think the concern here is so much that s=
ome people want to increase block size. It=E2=80=99s the *way* in which thi=
s change is being pushed that is deeply problematic.</div><div><br><blockqu=
ote type=3D"cite"><div><div dir=3D"ltr"><div><div><div><div class=3D"gmail_=
extra"><div class=3D"gmail_quote">On Sat, Aug 15, 2015 at 5:32 PM, Eric Lom=
brozo via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundati=
on.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=
=3D"word-wrap:break-word"><div>You deeply disappoint me, Mike.</div><div><b=
r></div><div>Not only do you misrepresent many cogent, well thought out pos=
itions from a great number of people who have published and posted a number=
 of articles detailing an explaining in-depth technical concerns=E2=80=A6yo=
u also seem to fancy yourself more capable of reading into the intentions o=
f someone who disappeared from the scene years ago, before we even were ful=
ly aware of many things we now know that bring the original =E2=80=9Cplan=
=E2=80=9D into question.</div><div><br></div><div>I ask of you, as a civili=
zed human being, to stop doing this divisive crap. Despite your protestatio=
ns to the contrary, YOU are the one who is proposing a radical departure fr=
om the direction of the project. Also, as several of us have clearly stated=
 before, equating the fork of an open source project with a fork of a crypt=
oledger is completely bogus - there=E2=80=99s a lot of other people=E2=80=
=99s money at stake. This isn=E2=80=99t a democracy - consensus is all or n=
othing. The fact that a good number of the people most intimately familiar =
with the inner workings of Satoshi=E2=80=99s invention do not believe doing=
 this is a good idea should give you pause.</div><div><br></div><div>Please=
 stop using Bitcoin as your own political football=E2=80=A6for the sake of =
Bitcoin=E2=80=A6and for your own sake. Despite your obvious technical abili=
ties (and I sincerely do believe you have them) you are discrediting yourse=
lf and hurting your own reputation.</div><div><br></div><div><br></div><div=
>- Eric</div><div><br></div><div><div><blockquote type=3D"cite"><div>On Aug=
 15, 2015, at 10:02 AM, Mike Hearn via bitcoin-dev &lt;<a href=3D"mailto:bi=
tcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.li=
nuxfoundation.org</a>&gt; wrote:</div><br><div><div dir=3D"ltr">Hello,<div>=
<br></div><div>As promised, we have released Bitcoin XT 0.11A which include=
s the bigger blocks patch set. You can get it from</div><div><br></div><div=
>=C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitcoinxt.software/" target=3D"_bla=
nk">https://bitcoinxt.software/</a><br></div><div><br></div><div>I feel sad=
 that it&#39;s come to this, but there is no other way. The Bitcoin Core pr=
oject has drifted so far from the principles myself and many others feel ar=
e important, that a fork is the only way to fix things.</div><div><br></div=
><div>Forking is a natural thing in the open source community, Bitcoin is n=
ot the first and won&#39;t be the last project to go through this. Often in=
 forks, people say there was insufficient communication. So to ensure every=
thing is crystal clear I&#39;ve written a blog post and a kind of &quot;man=
ifesto&quot; to describe why this is happening and how XT plans to be diffe=
rent from Core (assuming adoption, of course).</div><div><br></div><div>The=
 article is here:</div><div><br></div><div>=C2=A0 =C2=A0 <a href=3D"https:/=
/medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1" target=3D"_bla=
nk">https://medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1</a><=
br></div><div><br></div><div>It makes no attempt to be neutral: this explai=
ns things from our point of view.</div><div><br></div><div>The manifesto is=
 on the website.</div><div><br></div><div>I say to all developers on this l=
ist: if you also feel that Core is no longer serving the interests of Bitco=
in users, come join us. We don&#39;t bite.</div><div><br></div></div>
_______________________________________________<br>bitcoin-dev mailing list=
<br><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.linuxfoundation.org</a><br><a href=3D"https://lists.l=
inuxfoundation.org/mailman/listinfo/bitcoin-dev" target=3D"_blank">https://=
lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br></div></block=
quote></div><br></div></div><br>___________________________________________=
____<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
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>
<br></blockquote></div><br></div></div></div></div></div>
_______________________________________________<br>bitcoin-dev mailing list=
<br><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.linuxfoundation.org</a><br><a href=3D"https://lists.l=
inuxfoundation.org/mailman/listinfo/bitcoin-dev" target=3D"_blank">https://=
lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br></div></block=
quote></div><br></div></blockquote></div><br></div></div></div></div></div>
<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>
<br></blockquote></div>

--001a113f9694521c21051d61760e--