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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bryan@blockcypher.com>) id 1YyPjL-0003HD-Gj
for bitcoin-development@lists.sourceforge.net;
Fri, 29 May 2015 19:14:07 +0000
Received: from mail-oi0-f47.google.com ([209.85.218.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YyPjK-00008q-LZ
for bitcoin-development@lists.sourceforge.net;
Fri, 29 May 2015 19:14:07 +0000
Received: by oiww2 with SMTP id w2so63774915oiw.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 29 May 2015 12:14:01 -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=ZzkiIt8PGADS633u3LOF564TPv1tSl6jWvhdkXu/nfs=;
b=Xoe/yRoSmhwAnOFXM/sQGNXDANwkOzFE7C1gZI2brDFgvkvSsaL/XkWDjq2ZA6Jpvi
E132G3co9/icrHupQqNK6rtv1ZT6yQ4caC353nuj/eZXwGHEiQKpg5Djn41RDD8Rwv2s
pCyHjHyZpjBo5F2cIl2nvux9riEmoKNuKoZTWAPo/Yx9rVP46oJklj0MifbOga/7ENsz
ywz/VKSPToi8u1OtTVlgC+9eE7RgKg18+SI33Hz2o+t5GN8TAa0kY1zxgmMdVKAABBr/
YH1XkbVLL7Rx62wH9V1cMZ4cxsLr7er1FUk9BqFdEuVK1qFFAVk4OHtwq0U/I2yT98+D
MfXA==
X-Gm-Message-State: ALoCoQkhEcl8gzrk5mxulFnGosQ/pnCekGeaV6r6o2b26Xrf8T7Z1Ogct7vhAPINp/iv3QhcFnEd
MIME-Version: 1.0
X-Received: by 10.60.45.201 with SMTP id p9mr93570oem.82.1432925251243; Fri,
29 May 2015 11:47:31 -0700 (PDT)
Received: by 10.182.86.4 with HTTP; Fri, 29 May 2015 11:47:31 -0700 (PDT)
In-Reply-To: <CABsx9T23r_y2R9OEgqb3AAZf47Hh8BUJncjxxmPp5v_9uKEiqQ@mail.gmail.com>
References: <16096345.A1MpJQQkRW@crushinator>
<CABsx9T3-zxCAagAS0megd06xvG5n-3tUL9NUK9TT3vt7XNL9Tg@mail.gmail.com>
<CANEZrP3VCaFsW4+gPm2kCJ9z7oVUZYVaeNf=_cJWEWwh4ZxiPQ@mail.gmail.com>
<CABsx9T21zjHyO-nh1aSBM3z4Bg015O0rOfYq7=Sy4mf=QxUVQA@mail.gmail.com>
<CANEZrP2BaKwhpPgcUHWAHswOmUeFLgEk4ysrn4+73qNzWDJ=yQ@mail.gmail.com>
<CABsx9T3nCJ-w_v-yEbEE2Ytb+xC65mhYqhoAhoOHw9tkPpG0TA@mail.gmail.com>
<CANEZrP1qH+zucYsGrMgnfi99e61Edxaj+xm=u_xYXga1g0WzJQ@mail.gmail.com>
<CAE-z3OVmw+0doCe0hmYE6A1D61h0AUh4Mtnf5Fg1e4zQBkpraQ@mail.gmail.com>
<CANEZrP0psA7hcJdKdA-r01UEt7ig3O-9vjwBMqKSEq-csu0hPQ@mail.gmail.com>
<CABsx9T23r_y2R9OEgqb3AAZf47Hh8BUJncjxxmPp5v_9uKEiqQ@mail.gmail.com>
Date: Fri, 29 May 2015 11:47:31 -0700
Message-ID: <CANeMN=8Q3CF6kfA+4X8Rf0HHWwjEJ5kb4ePgHccWgGJ2CPz3eA@mail.gmail.com>
From: Bryan Cheng <bryan@blockcypher.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1d9aa973e9605173ce87c
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YyPjK-00008q-LZ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
function
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: Fri, 29 May 2015 19:14:07 -0000
--001a11c1d9aa973e9605173ce87c
Content-Type: text/plain; charset=UTF-8
On Fri, May 29, 2015 at 5:39 AM, Gavin Andresen <gavinandresen@gmail.com>
wrote:
> What do other people think?
>
>
> If we can't come to an agreement soon, then I'll ask for help
> reviewing/submitting patches to Mike's Bitcoin-Xt project that implement a
> big increase now that grows over time so we may never have to go through
> all this rancor and debate again.
>
> I'll then ask for help lobbying the merchant services and exchanges and
> hosted wallet companies and other bitcoind-using-infrastructure companies
> (and anybody who agrees with me that we need bigger blocks sooner rather
> than later) to run Bitcoin-Xt instead of Bitcoin Core, and state that they
> are running it. We'll be able to see uptake on the network by monitoring
> client versions.
>
>
>
While I think we'd all prefer Core to make changes like this, the current
environment may make that impossible. If this change happens in XT, we will
support the necessary changes in our own implementation. The block size
limit is a problem _today_, and I'd rather we solve today's problems with
today's understanding rather than let speculation about future unknowns
stop our ability to respond to known issues.
--001a11c1d9aa973e9605173ce87c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, May 29, 2015 at 5:39 AM, Gavin Andresen <span dir=3D"ltr"><<a href=
=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.c=
om</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"=
>What do other people think?<div><br></div><div><br></div><div>If we can=
9;t come to an agreement soon, then I'll ask for help reviewing/submitt=
ing patches to Mike's Bitcoin-Xt project that implement a big increase =
now that grows over time so we may never have to go through all this rancor=
and debate again.</div><div><br></div><div>I'll then ask for help lobb=
ying the merchant services and exchanges and hosted wallet companies and ot=
her bitcoind-using-infrastructure companies (and anybody who agrees with me=
that we need bigger blocks sooner rather than later) to run Bitcoin-Xt ins=
tead of Bitcoin Core, and state that they are running it. We'll be able=
to see uptake on the network by monitoring client versions.</div><div><br>=
</div><div><br></div></div></blockquote><div><br></div><div>While I think w=
e'd all prefer Core to make changes like this, the current environment =
may make that impossible. If this change happens in XT, we will support the=
necessary changes in our own implementation. The block size limit is a pro=
blem _today_, and I'd rather we solve today's problems with today&#=
39;s understanding rather than let speculation about future unknowns stop o=
ur ability to respond to known issues.</div></div><br></div></div>
--001a11c1d9aa973e9605173ce87c--
|
