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
|
Return-Path: <yifu@coinapex.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9DEC1273
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Aug 2015 12:29:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f200.google.com (mail-ig0-f200.google.com
[209.85.213.200])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C8CD513A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Aug 2015 12:29:02 +0000 (UTC)
Received: by igcse8 with SMTP id se8so26768845igc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Aug 2015 05:29:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coinapex.com; s=google;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type; bh=HMdrNMFet2je8DYRGzIIosqERDd6fytGPGrincs+jH0=;
b=WElp5LGgEPes1kCLnwybP00xumFKVqW78iXEF03fWLMpkcCDvEtFFU7IVYNkkocqBk
UkYx+RAQ1Pjf/xP98gIeTyaNYgPNhiHsJ+MMvaxddlXUhuyTgF27057jiOBa0yaYaeAn
w3Bjh9arYhjotdZg3W9rduRzWF3rYm/1tuS6c=
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:content-type;
bh=HMdrNMFet2je8DYRGzIIosqERDd6fytGPGrincs+jH0=;
b=K2r3rixvW29/MwGFbux4M7qAqVeNPA2xIRWtvYQG2w6eRxhOIXnZiM51W+nM1J9nUw
hi1KXuXDhhxUydOOfGk85x0uaeYKgLeH71LD3WUrr0wYHiFfm/QBYDzmX07Q6D7TB0Hp
zYH4+M3wAx90bROpkmSsTjiEov088OUA/9Auwkl7SaakwJMgJC0pOSBfW/UdvfftQ7m3
6rSCmDqVUg3aCZmWjbJR0TCc9+nKfFMzAv/R55lgJ6eMD9tk0uGkHztZnxWEwAgDINfO
jtsJVQxr5PwV/TxthjdvQUrqJVtvHmBa/ka31ekKsXrHGvAvOdPquAnhTKstpt8ww9Cm
N5RQ==
X-Gm-Message-State: ALoCoQmlwq1Y4p1VEylhpoeWOfy/HCjPZSVPPAlP8Ap1rmBSiojgL6UZUNUzrSgD8r3xXf5yhfpa
X-Received: by 10.60.93.99 with SMTP id ct3mr7933430oeb.56.1440160142127; Fri,
21 Aug 2015 05:29:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.84.69 with HTTP; Fri, 21 Aug 2015 05:28:22 -0700 (PDT)
In-Reply-To: <CADJgMzuBKauAX_tf4ZCxtErfz9Rq7ri3=8S9ZiKou6CPwP8cQw@mail.gmail.com>
References: <CA+1nnrk1EWd7rhwj91p1rqgGVFgOT4UYq=+Nmq41sHJYmy7YYA@mail.gmail.com>
<CAAS2fgR4bsJtC99-fK1L+FsQT7vOfOpz9FOVqvAnqbpkaRJHLQ@mail.gmail.com>
<BE291934-F40A-4163-834C-6B3FFBD7C4E0@petertodd.org>
<CADJgMzucVKgQQtzwBNMcU3Vy=ae+2jMQY=am_xYXcKtyforpUg@mail.gmail.com>
<3B2A58B3-6AF6-4F1C-A6FA-7AEC97F48AD0@petertodd.org>
<CAHcfU-XrSA6p_2AJJ1W6KmatkEZdvh1W4ruA-upq4wPWoaJTNQ@mail.gmail.com>
<CADJgMzuBKauAX_tf4ZCxtErfz9Rq7ri3=8S9ZiKou6CPwP8cQw@mail.gmail.com>
From: Yifu Guo <yifu@coinapex.com>
Date: Fri, 21 Aug 2015 08:28:22 -0400
Message-ID: <CAHcfU-U2KHmaDUvtASY5+oHE1OmEzHG8MZcx_ar6uM2oCU5Smw@mail.gmail.com>
To: Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=047d7b33d952b11072051dd16959
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,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
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all
BIPs on this website ?
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: Fri, 21 Aug 2015 12:29:03 -0000
--047d7b33d952b11072051dd16959
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
accordingly to public release[1], They.
1. agreed that blocksize increase is needed.
2. opposed original 20mb, suggest 8mb instead as it is more technically
reasonable.
3. do not want blocksize to change in the "short term future" ( direct
translation. ) and in the document states.
"after discussion we are in agreement that the blocksize should be within
the ball park of 8mb for the short term future."
They have no explicitly rejected or supported the other components of
BIP101. It's my opinion that as long as the change is < 8mb. they'll take
it.
I don't believe in trying to predict the future, on adoption, technology
growth, nor geopolitics. I think it matters very little which BIP we need
up deploying, as long as all the attack vectors are covered, especially for
the dynamically adjustable ones.
One thing is for sure though, not increasing the blocksize is not an option=
.
we can't predict the future, in the mean time, Hardfork Responsibly=E2=84=
=A2.
[1]
http://7fvhfe.com1.z0.glb.clouddn.com/@/wp-content/uploads/2015/06/%E5%8C%B=
A%E5%9D%97%E6%89%A9%E5%AE%B9%E8%8D%89%E6%A1%88.jpg
On Fri, Aug 21, 2015 at 7:28 AM, Btc Drak <btcdrak@gmail.com> wrote:
> On Fri, Aug 21, 2015 at 11:55 AM, Yifu Guo via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I like the intend of this attempt to bring more clarity to the blocksiz=
e
> > debate, however it would be more help to make this a information site
> about
> > the current outstanding BIPs and summarize their differences rather tha=
n
> > voting mechanism.
> > (ofcourse the author of the BIPs would "vote" for their own proposals.=
)
> >
> > It would be good to include supporting and counter statements regards t=
o
> > these BIPs on the site.
> > in addition to highlight certain things like pools in china have voiced
> > their opinion that increase should happen, and 8mb is something they ar=
e
> > comfortable with, which is not directly related to a single BIP, but
> never
> > the less relevant in this discussion.
>
> I was rather surprised by the tweet from AntPool[1] today saying that
> they support big blocks and would be prepared to upgrade to XT. Pools
> have stated that they are willing to increase to a maximum of 8MB, but
> upgrading to XT puts them on a schedule towards 8GB which is clearly
> not what they have agreed to.
>
> Do you have any insights into what's going on there?
>
> Also do you have any insight into what Chinese pools would accept as a
> compromise in terms of raising the blocksize limit?
>
> Drak
>
> [1] https://twitter.com/JihanWu/status/633288343338381314
>
--=20
*Yifu Guo*
*"Life is an everlasting self-improvement."*
--047d7b33d952b11072051dd16959
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><span style=3D"font-size:12.8px">accordingly to public rel=
ease[1], They.</span><div style=3D"font-size:12.8px"><br></div><div style=
=3D"font-size:12.8px">1. agreed that blocksize increase is needed.</div><di=
v style=3D"font-size:12.8px">2. opposed original 20mb, suggest 8mb instead =
as it is more technically reasonable.</div><div style=3D"font-size:12.8px">=
3. do not want blocksize to change in the "short term future" ( d=
irect translation. ) and in the document states.</div><div style=3D"font-si=
ze:12.8px">"after discussion we are in agreement that the blocksize sh=
ould be within the ball park of 8mb for the short term future."</div><=
div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">Th=
ey have no explicitly rejected or supported the other components of BIP101.=
It's my opinion that as long as the change is < 8mb. they'll ta=
ke it.</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-si=
ze:12.8px">I don't believe in trying to predict the future, on adoption=
, technology growth, nor geopolitics. I think it matters very little which =
BIP we need up deploying, as long as all the attack vectors are covered, es=
pecially for the dynamically adjustable ones.</div><div style=3D"font-size:=
12.8px"><br></div><div style=3D"font-size:12.8px">One thing is for sure tho=
ugh,=C2=A0<span style=3D"font-size:12.8px">not increasing the blocksize is =
not an option.</span></div><div style=3D"font-size:12.8px"><br></div><div s=
tyle=3D"font-size:12.8px">we can't predict the future, in the mean time=
, Hardfork Responsibly<span style=3D"font-family:Arial,Verdana,Helvetica,sa=
ns-serif;font-size:14px">=E2=84=A2</span><span style=3D"font-size:12.8px">.=
</span></div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-s=
ize:12.8px"><span style=3D"font-size:12.8px">[1]</span><a href=3D"http://7f=
vhfe.com1.z0.glb.clouddn.com/@/wp-content/uploads/2015/06/%E5%8C%BA%E5%9D%9=
7%E6%89%A9%E5%AE%B9%E8%8D%89%E6%A1%88.jpg" style=3D"font-size:12.8px" targe=
t=3D"_blank">http://7fvhfe.com1.z0.glb.clouddn.com/@/wp-content/uploads/201=
5/06/%E5%8C%BA%E5%9D%97%E6%89%A9%E5%AE%B9%E8%8D%89%E6%A1%88.jpg</a><br></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug 21,=
2015 at 7:28 AM, Btc Drak <span dir=3D"ltr"><<a href=3D"mailto:btcdrak@=
gmail.com" target=3D"_blank">btcdrak@gmail.com</a>></span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><span>On Fri, Aug 21, 2015 at 11:55 AM, Yifu Gu=
o via bitcoin-dev<br>
<<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
</span><span>> I like the intend of this attempt to bring more clarity t=
o the blocksize<br>
> debate, however it would be more help to make this a information site =
about<br>
> the current outstanding BIPs and summarize their differences rather th=
an<br>
> voting mechanism.<br>
>=C2=A0 (ofcourse the author of the BIPs would "vote" for thei=
r own proposals.)<br>
><br>
> It would be good to include supporting and counter statements regards =
to<br>
> these BIPs on the site.<br>
> in addition to highlight certain things like pools in china have voice=
d<br>
> their opinion that increase should happen, and 8mb is something they a=
re<br>
> comfortable with, which is not directly related to a single BIP, but n=
ever<br>
> the less relevant in this discussion.<br>
<br>
</span><div><div>I was rather surprised by the tweet from AntPool[1] today =
saying that<br>
they support big blocks and would be prepared to upgrade to XT. Pools<br>
have stated that they are willing to increase to a maximum of 8MB, but<br>
upgrading to XT puts them on a schedule towards 8GB which is clearly<br>
not what they have agreed to.<br>
<br>
Do you have any insights into what's going on there?<br>
<br>
Also do you have any insight into what Chinese pools would accept as a<br>
compromise in terms of raising the blocksize limit?<br>
<br>
Drak<br>
<br>
[1] <a href=3D"https://twitter.com/JihanWu/status/633288343338381314" rel=
=3D"noreferrer" target=3D"_blank">https://twitter.com/JihanWu/status/633288=
343338381314</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div><div dir=3D"ltr"><span style=3D"font-size:small;color:rgb(136,136,136)=
"><font face=3D"garamond, serif" size=3D"4"><b>Yifu Guo</b></font></span><d=
iv style=3D"font-size:small"><font face=3D"verdana, sans-serif"><div style=
=3D"font-size:13px"><font size=3D"1" color=3D"#333333"><i>"Life is an =
everlasting self-improvement."</i></font></div></font></div></div></di=
v>
</div></div>
--047d7b33d952b11072051dd16959--
|
