summaryrefslogtreecommitdiff
path: root/6b/160f550fad913413c3cbec53c46a5e47675e47
blob: 512cf13229e0f2d45225a89c181fefca923a319f (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
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 4609A41C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Apr 2017 07:04:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com
	[209.85.213.42])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C1EE1F1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Apr 2017 07:04:46 +0000 (UTC)
Received: by mail-vk0-f42.google.com with SMTP id r69so45439496vke.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 15 Apr 2017 00:04:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc:content-transfer-encoding;
	bh=SJyqs/oZN81cOHv426B90Ut6yOoay+vK6ACRZ/pM0f0=;
	b=TNC+P7oJfDyDxmGqHfiFJb0w1PbUNGGVG8JmECzrpidFM5Gcq6K9yAaAJ3Z2CKUByl
	KreU+qrAZhTQIVYBpiA4epX+xU8cObD2XIegHCjM8bCPt8F7/Q4W4XLawFvXUruDwC8Y
	KSDcRT460/YoDJfwSJ1An0MEYGmKJ3YOWo5jJ4lGseXuIMptkwpgHUD1CxoPexk8mdQ7
	vuDtntgoqcrY5dh+EBql6v2TX2pB/EX6qp1lkejTIkxODVDjbgsZXDy9NmMDNmfc2hWX
	i2PpvgR9A9KJZVq9XqoFrGq3ochAb96fklB5xcCEyXG22ZhWgKjY5sdNn7oZy3csTXbP
	MVzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to:cc:content-transfer-encoding;
	bh=SJyqs/oZN81cOHv426B90Ut6yOoay+vK6ACRZ/pM0f0=;
	b=Q0TjNqO61ni8IqWX4lkS5LF23jhGvfnhoQTLCiSi4FogHKC1MnkXmVjMexiRfzNB6+
	N+2D6OcucsQUD5xPDSuo20dAsojA8N3EMa/Tx7mdb194LcsRt/bm7CZrgN/8yOSI5s5B
	nKRUyhHHsYvYD1eMQVT2u5vT9heMV3IBFIoCU27wuTmNekJ8TEtHElu2vjAADh0/N6l8
	c8/WQqcIdrtCNQfMG1WEiOUA+Dm3HqJJFejAElOeTtJQAWz+oX8qg41K24ZPLz7GPe4+
	Nx0iXwnxaZjnyqfzThJuOdfmn1r7L+4GmCBkQo26GmrCP65b+Q1Snsq0HYi7OjuCm2//
	hWOQ==
X-Gm-Message-State: AN3rC/6ywyCOwBIyrZlOh6j7o1gOuZsp6xmt5MDm1YUdv37lJzMCUW6m
	iGM+Dg6FFB24wpx3jLNma24aaJ3g4g==
X-Received: by 10.31.74.132 with SMTP id x126mr4867995vka.20.1492239885932;
	Sat, 15 Apr 2017 00:04:45 -0700 (PDT)
MIME-Version: 1.0
Sender: gmaxwell@gmail.com
Received: by 10.103.94.132 with HTTP; Sat, 15 Apr 2017 00:04:45 -0700 (PDT)
In-Reply-To: <E7A3E345-15C9-4C4C-B3D7-C75634243430@gmail.com>
References: <CAAS2fgRdSOu8N6L3+fBpnye+rM+W6+F=cePy=9oL4tJuCj=Jsw@mail.gmail.com>
	<E7A3E345-15C9-4C4C-B3D7-C75634243430@gmail.com>
From: Gregory Maxwell <greg@xiph.org>
Date: Sat, 15 Apr 2017 07:04:45 +0000
X-Google-Sender-Auth: 0zEmiu6cNPqHdQy3obXps1ySYwU
Message-ID: <CAAS2fgSXOkTcJ5tTssuGMCQwh-JFQTkzU5VBjaR+hKT+bD3Q6A@mail.gmail.com>
To: Cameron Garnham <da2ce7@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, 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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] I do not support the BIP 148 UASF
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: Sat, 15 Apr 2017 07:04:47 -0000

On Sat, Apr 15, 2017 at 6:28 AM, Cameron Garnham <da2ce7@gmail.com> wrote:
> As many may remember, there was quite some controversy about the BIP16 vs=
 BIP 17 split; the main argument for BIP16 was the urgency of P2SH, and how=
 this was the already =E2=80=9Ctested and proven to work=E2=80=9D solution.

And as a result we ultimately got a clearly inferior solution (520
byte script limit; 80-bit security; months of orphaned blocks-- and
two of those were not issues in BIP17).  I went along for the cram
fest on 16 after 12 caught fire, and I was mistaken to do so.

Doubly so because it took years for P2SH to achieve any kind of mass
deployment due to issues far away from consensus.  An extra two months
spent on some ground-work (including communications and documentation)
could have pulled forward practical deployment by a year and given
time to find and fix some of the flaws in the design of P2SH.

> BIP 148 is out (our?) terms of peace.  The Bitcoin Community is tired-to-=
death of this war and wants a resolution swiftly. BIP 148 proves a outlet, =
and in Maxwell words: =E2=80=9C...almost guarantees at a minor level of dis=
ruption.=E2=80=9D.

It seems I lost a word in my comment: that should have been "almost
guarantees at _least_ a minor level of disruption". A minor level of
disruption is the _minimum_ amount of disruption, and for no good
reason except an unprecedented and unjustified level of haste.

Considering that you did not spare a single word about the specific
property that I am concerned about-- that the proposal will reject the
blocks of passive participants, due to avoidable design limitations--
I can't help but feel that you don't even care to understand the
concern I was bringing up. :(

How many people barely reviewed the specifics of the proposal simply
because they want something fast and this proposal does something
fast?

> tired-to-death of this war and wants a resolution swiftly

By now competitors and opponents to Bitcoin have surely realized that
they can attack Bitcoin by stirring up drama.

As a result, the only way that we will ever be free from "war" is if
we choose to not let it impact us as much as possible. We must be
imperturbable and continue working at the same level of excellence as
if virtual shells weren't flying overhead-- or otherwise there is an
incentive to keep them flying 24/7. Internet drama is remarkably cheap
to generate. "The only thing we have to fear is fear itself".

The alternative is that we hand opponents a ready made formula for
disruption: astroturf enough drama up that Bitcoiners "sacrifice
correctness" themselves right off a cliff in a futile attempt to make
it go away. :)