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
|
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 62959ACB
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 19:12:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com
[209.85.223.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 044F4143
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 19:12:00 +0000 (UTC)
Received: by iebrt9 with SMTP id rt9so81773511ieb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 12:12:00 -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=+NGKtT3PO0lI1UEQD7Cp5WMHItMPq0c3Utoj+UonOZI=;
b=Qs0jOLZ0QThfQgcsXIX5BadwGqHxU01DBnp4x+hJxJOggye/6cpzEwY/0wwpsXoQQx
07vdovqfKHI2eK/jtdUZh105ki3vjW780EaMHowPVbO48z9ynN2CarR4kEz2nIkdOav+
5Xl1nsP8rJzGfO3zyPjhPqbnL0opl/ECCZ25ENlcZh45Efdt26qm01OxFzM/i1jogZfI
44PIApT1aahvvGuQ6AHhuuU+p2Rnpx6pL0JHfqxsekaPeYmBeI8E6id8dPxCx6DMDzdH
5AOA/Ga0LIvdSd0UN8pdmsDfNecWLVTH8Uor8Y6J5x3n4SQKrplmZ/mDpEfJsuSuaZBY
tvIQ==
X-Gm-Message-State: ALoCoQnzl1swg5n/MJH9F45WDHN/V3tD0CZxNVZOrtzH6ymC0FJbdhkSSfvTHmmw64yP2MmzXU+9
MIME-Version: 1.0
X-Received: by 10.43.40.130 with SMTP id tq2mr5338094icb.46.1435345920500;
Fri, 26 Jun 2015 12:12:00 -0700 (PDT)
Received: by 10.107.149.20 with HTTP; Fri, 26 Jun 2015 12:12:00 -0700 (PDT)
X-Originating-IP: [208.54.4.150]
Received: by 10.107.149.20 with HTTP; Fri, 26 Jun 2015 12:12:00 -0700 (PDT)
In-Reply-To: <CAE-z3OUZJ2STEMf0yMWTyvcVjFEuh0DfX4mc+XhBsykh7GdOGw@mail.gmail.com>
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
<CADm_Wca+ow4pMzN7SyKjsMdFo0wuUerYYjf5xKs5G_2Q2PzMmA@mail.gmail.com>
<CAPg+sBg=sn7djO_8H16NDg7S7m7_0eTcrgLVofMWQ2ANz+jw9w@mail.gmail.com>
<CADm_WcbQog_UCV=JPHyqTRxKbaGY7jedtHE_D8jJSe_thMg05w@mail.gmail.com>
<558D9E49.7000601@gmail.com>
<CAE-z3OUZJ2STEMf0yMWTyvcVjFEuh0DfX4mc+XhBsykh7GdOGw@mail.gmail.com>
Date: Fri, 26 Jun 2015 12:12:00 -0700
Message-ID: <CAOG=w-uxTvKusuJmDGcD76hJtXbdPq1g7hm0-48H1qr7jntN3Q@mail.gmail.com>
From: Mark Friedenbach <mark@friedenbach.org>
To: Tier Nolan <tier.nolan@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51dd849b8c05e051970834d
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@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
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, 26 Jun 2015 19:12:01 -0000
--bcaec51dd849b8c05e051970834d
Content-Type: text/plain; charset=UTF-8
This is a hard fork. It is not about miners, at all. 2013 showed that when
there is true consensus mining can be coordinated on the order of hours or
days. This is about pushing through a coercive change to the
decentralization tradeoffs of bitcoin without unanimous consent.
On Jun 26, 2015 12:03 PM, "Tier Nolan" <tier.nolan@gmail.com> wrote:
> On Fri, Jun 26, 2015 at 7:47 PM, Patrick Strateman <
> patrick.strateman@gmail.com> wrote:
>
>> For a proposed hard fork to reach a level of consensus necessary to be
>> safe requires that there be a clear and self evident course of action.
>>
>
> Safety increases with more lead-in time. If the reference client was
> updated so that the hard fork happened in two years, it would be pretty
> safe. Miners would have time to update.
>
> If miners (or the community) objected, it is sort of like a game of
> chicken.
>
> This is one of the problems with not making decisions in advance, the
> resulting hard fork is inherently safer.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--bcaec51dd849b8c05e051970834d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">This is a hard fork. It is not about miners, at all. 2013 sh=
owed that when there is true consensus mining can be coordinated on the ord=
er of hours or days. This is about pushing through a coercive change to the=
decentralization tradeoffs of bitcoin without unanimous consent.</p>
<div class=3D"gmail_quote">On Jun 26, 2015 12:03 PM, "Tier Nolan"=
<<a href=3D"mailto:tier.nolan@gmail.com">tier.nolan@gmail.com</a>> w=
rote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r">On Fri, Jun 26, 2015 at 7:47 PM, Patrick Strateman <span dir=3D"ltr"><=
;<a href=3D"mailto:patrick.strateman@gmail.com" target=3D"_blank">patrick.s=
trateman@gmail.com</a>></span> wrote:<br><div class=3D"gmail_extra"><div=
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
For a proposed hard fork to reach a level of consensus necessary to
be safe requires that there be a clear and self evident course of
action.<br></div></blockquote><div><br></div><div>Safety increases with=
more lead-in time.=C2=A0 If the reference client was updated so that the h=
ard fork happened in two years, it would be pretty safe.=C2=A0 Miners would=
have time to update.<br><br></div><div>If miners (or the community) object=
ed, it is sort of like a game of chicken.<br><br></div><div>This is one of =
the problems with not making decisions in advance, the resulting hard fork =
is inherently safer.<br></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>
--bcaec51dd849b8c05e051970834d--
|
