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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Z5hpR-0003T4-74
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 21:58:33 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.218.42 as permitted sender)
client-ip=209.85.218.42; envelope-from=jgarzik@bitpay.com;
helo=mail-oi0-f42.google.com;
Received: from mail-oi0-f42.google.com ([209.85.218.42])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5hpQ-0003W7-CT
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 21:58:33 +0000
Received: by oigb199 with SMTP id b199so25981768oig.3
for <bitcoin-development@lists.sourceforge.net>;
Thu, 18 Jun 2015 14:58:27 -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:from:date
:message-id:subject:to:cc:content-type;
bh=iJM9WuEplm/AQHKFuEkXWwy4h6kDYubqABrcHusK4s0=;
b=P0A5IR87jt48vO3KieKwLi1Ex59WZ5D2JIvYRPgLgP31cSTdphy5dDtLR5/WEY+XXS
fPJMGA4KBJIOJzSnwWrc6su3DNV3DrwexCxui5+65aIixypzs6d5TcxmapgJH+4EKRgo
/gp+QkCITQEQtvnxnFgZMGuyfhROq++TVCk6176ke5+4BLitTYLz8+oxBGqwLt8kfwsI
UfJ5WSFGHhnNeiZvRnWbY0SOJLg7SKlhZVTg6r2DlKb4bCDLfDt0m7IXYD1uSUUO4zcQ
GYMDDZcWwkWpQHSf3lBYjft5NV3qLNis59h8ABXESla87SRZgIYgAVPqY+YOLC1YWawO
o/nQ==
X-Gm-Message-State: ALoCoQnXRcw1qFH363QrvER6MLwxxg8ujQNogq7o+m/7kkAUsDAUWukv0Ww9rVTJ1FY3vGIPkuv1
X-Received: by 10.182.86.9 with SMTP id l9mr10851150obz.61.1434664706941; Thu,
18 Jun 2015 14:58:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.149 with HTTP; Thu, 18 Jun 2015 14:58:06 -0700 (PDT)
In-Reply-To: <CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>
References: <55828737.6000007@riseup.net>
<CABm2gDoa7KxsgvREo3yiNjfd6AeayqAqkjMe2rvX8yyxR_ddcA@mail.gmail.com>
<55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator>
<CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 18 Jun 2015 14:58:06 -0700
Message-ID: <CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com>
To: Mark Friedenbach <mark@friedenbach.org>
Content-Type: multipart/alternative; boundary=089e014954c83ace7a0518d1e821
X-Spam-Score: -0.2 (/)
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 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.4 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z5hpQ-0003W7-CT
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Gavin Andresen <gavin@bitcoinfoundation.org>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
to Remove Commit Access from Other Developers
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 Jun 2015 21:58:33 -0000
--089e014954c83ace7a0518d1e821
Content-Type: text/plain; charset=UTF-8
Is that a forward-looking position? It does not seem so.
The whole point is getting out in front of the need, to prevent significant
negative impact to users when blocks are consistently full.
To do that, you need to (a) plan forward, in order to (b) set a hard fork
date in the future.
"We don't see a need today" is therefore useless, because when you do reach
X day when need is apparent, the best solution then becomes an immediate
fork for which the network and markets are not prepared.
Failing to resolve the block size issue soon will simply result in most
businesses assuming relevant Bitcoin Core standards process is failing, and
proceed with the Bitcoin-XT fork.
As I've said on IRC, the "do nothing, for now" position is untenable.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--089e014954c83ace7a0518d1e821
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Is that a forward-looking position?=C2=A0 It does not seem=
so.<div><br></div><div>The whole point is getting out in front of the need=
, to prevent significant negative impact to users when blocks are consisten=
tly full.</div><div><br></div><div>To do that, you need to (a) plan forward=
, in order to (b) set a hard fork date in the future.</div><div><br></div><=
div>"We don't see a need today" is therefore useless, because=
when you do reach X day when need is apparent, the best solution then beco=
mes an immediate fork for which the network and markets are not prepared.</=
div><div><br></div><div>Failing to resolve the block size issue soon will s=
imply result in most businesses assuming relevant Bitcoin Core standards pr=
ocess is failing, and proceed with the Bitcoin-XT fork.</div><div><br></div=
><div>As I've said on IRC, the "do nothing, for now" position=
is untenable.</div><div><br></div><div class=3D"gmail_extra">-- <br><div c=
lass=3D"gmail_signature">Jeff Garzik<br>Bitcoin core developer and open sou=
rce evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpa=
y.com/" target=3D"_blank">https://bitpay.com/</a></div>
</div></div>
--089e014954c83ace7a0518d1e821--
|
