summaryrefslogtreecommitdiff
path: root/af/f7a72cc0fcb0ca8a635c8b48ecb81c6eee8fe4
blob: a17cae72e73c3abfc0e0857b0cd6a013a8d61558 (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
Return-Path: <alp.bitcoin@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 581F18DC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 28 Mar 2017 20:53:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pg0-f48.google.com (mail-pg0-f48.google.com [74.125.83.48])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CF536CD
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 28 Mar 2017 20:53:31 +0000 (UTC)
Received: by mail-pg0-f48.google.com with SMTP id n5so75909111pgh.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 28 Mar 2017 13:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=8Z+Gy+gJXwZ3rSV0eg8E0sr9rt4YJ9KiNnctHwBUiaE=;
	b=EGaeGdvO1gBcJpQe4W/5k8GFcpmZontG6e1QE/PPMWHFO5k458eEQ9WFHxQtcfMzKU
	v5eIPpSESPizPj2fs77MTPlK10UVhWfj8KNmtC1IczJxJpmLtwo6vdzB3+826HErDGGZ
	ZZ2MY+j+/O/+jm3nZYYXUIiFtTjw9ilbcCGqxkjkt3bTtyVGvpfdCxOVrP6jfxfHlTsZ
	2FF+tZtCyaNACRVoSGFL5t++9/Fl8TpyAnYcZw7EEIj4RbUErmh3GMmo5qSPLqGWpxIM
	ol9K0kJFfWsU2q+xqNnxD04J136Va/bstGJvMFl+hK5t3e5gl8BNW+93iRwtecxCWaku
	lO0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=8Z+Gy+gJXwZ3rSV0eg8E0sr9rt4YJ9KiNnctHwBUiaE=;
	b=tbxzCi9/aqmqsa617ppTmOr9bhMR+vy9DUnWegwp8WVg5ZVduu4wqvbOPNqnJ8aJBY
	Gn7CRxew6o9gtU4VV9N0ZBHVeYLALcUTf+s0ihG9T9GlZrzaCW36M9YLIkRgmcJhz24n
	gmqfpCYWSYRkjBg/pvNsDjbkjDmslOK7jeaAiw3TsqpaUvcg8c11KwEjo8j23q76Rb2m
	r7fw+7ubLXqKWC8dQ8HPZdMXpOoAXK2JwfRR60bdUv6QQp1auhrlnx7UL9bVOljOVSjq
	orP9lSKYOjqSlYyImaMyQSwVITkIfAAk6EtAkLwT9SfOd0a8CZ3gcxnTU8Ve8O2lNq+M
	CNPg==
X-Gm-Message-State: AFeK/H1tEYM9Zy6x9L01kkZ6mpaYcXM95oi2oWMWYGW+WgIwkk8icT4fOVm1bkQYknQl54POrP62beVG1Jp5jg==
X-Received: by 10.98.157.148 with SMTP id a20mr34263837pfk.144.1490734411483; 
	Tue, 28 Mar 2017 13:53:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.128.19 with HTTP; Tue, 28 Mar 2017 13:53:30 -0700 (PDT)
In-Reply-To: <10740865.BWG7G26IGS@cherry>
References: <CAAeo5+jSfp5XWj=EYJ_i-XS+=RjxfY-co7+b7iu3Gd=WWHbHzQ@mail.gmail.com>
	<10740865.BWG7G26IGS@cherry>
From: Alphonse Pace <alp.bitcoin@gmail.com>
Date: Tue, 28 Mar 2017 15:53:30 -0500
Message-ID: <CAMBsKS_Fp79jn_zSyzrcJU01Ri1hUtoVPoDf64mB-uDOEYEQbA@mail.gmail.com>
To: Tom Zander <tomz@freedommail.ch>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=94eb2c1165060d0dbf054bd0a708
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, 
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 28 Mar 2017 20:53:32 -0000

--94eb2c1165060d0dbf054bd0a708
Content-Type: text/plain; charset=UTF-8

His demand (not suggestion) allows it without any safeguards.

>This patch must be in the immediate next release of Bitcoin Core.

That is not a suggestion.

Wang - still waiting on the details of this meeting.  In the spirit of
openness, I think you ought to share with the community what kind of secret
meetings are happening.


On Tue, Mar 28, 2017 at 3:43 PM, Tom Zander via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Tuesday, 28 March 2017 21:56:49 CEST Paul Iverson via bitcoin-dev wrote:
> > It is clear that, spam aside, blocks are getting full and we need
> increase
> > them soon. What I don't like about your proposal is it forces all node
> > operators to implicitly accept larger blocks in 2020, even maybe against
> > their will. 32 MB blocks might result in a loss of decentralization, and
> > it might be too difficult to coordinate for small blocks before it's too
> > late.
>
> The suggestion was not to produce 32MB blocks, so your fear here is
> unfounded.
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">His demand (not suggestion) allows it without any safeguar=
ds.<div><br></div><div>&gt;<span style=3D"font-size:12.8px">This patch must=
 be=C2=A0</span><span style=3D"font-size:12.8px">in the immediate next rele=
ase of Bitcoin Core.</span></div><div><span style=3D"font-size:12.8px"><br>=
</span></div><div><span style=3D"font-size:12.8px">That is not a suggestion=
.</span></div><div><span style=3D"font-size:12.8px"><br>Wang - still waitin=
g on the details of this meeting.=C2=A0 In the spirit of openness, I think =
you ought to share with the community what kind of secret meetings are happ=
ening.</span></div><div><span style=3D"font-size:12.8px"><br></span></div><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar =
28, 2017 at 3:43 PM, Tom Zander via bitcoin-dev <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitco=
in-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">On Tuesday, 28 March 2017 21:56:49 CEST Paul=
 Iverson via bitcoin-dev wrote:<br>
&gt; It is clear that, spam aside, blocks are getting full and we need incr=
ease<br>
&gt; them soon. What I don&#39;t like about your proposal is it forces all =
node<br>
&gt; operators to implicitly accept larger blocks in 2020, even maybe again=
st<br>
&gt; their will. 32 MB blocks might result in a loss of decentralization, a=
nd<br>
&gt; it might be too difficult to coordinate for small blocks before it&#39=
;s too<br>
&gt; late.<br>
<br>
</span>The suggestion was not to produce 32MB blocks, so your fear here is<=
br>
unfounded.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Tom Zander<br>
Blog: <a href=3D"https://zander.github.io" rel=3D"noreferrer" target=3D"_bl=
ank">https://zander.github.io</a><br>
Vlog: <a href=3D"https://vimeo.com/channels/tomscryptochannel" rel=3D"noref=
errer" target=3D"_blank">https://vimeo.com/channels/<wbr>tomscryptochannel<=
/a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
_________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>

--94eb2c1165060d0dbf054bd0a708--