summaryrefslogtreecommitdiff
path: root/7e/24d2d7c0cc88338f89cc65c2c9d00fd726c9e5
blob: 9e6cbae0907085038eed9ae191405a2fae8654a6 (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
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id F1A7189D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 19 Aug 2015 18:22:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com
	[209.85.217.182])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 67CEB16B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 19 Aug 2015 18:22:19 +0000 (UTC)
Received: by lbbpu9 with SMTP id pu9so8848878lbb.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 19 Aug 2015 11:22:18 -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=YuVumobnn0G4yNdOy99jO4cqhjlzhKoQUWCJ7j6S21k=;
	b=apv96q4xkwz+L3UcsZPQRscExHyj9iIOxRaPETqfpsuAuf6cVmM1rIbAiR8kKnrrXL
	Nn27PxWtCzreo6vprYjg9+vht7Q7jparankZXbL2/2X8dRaNd3Ko12tR/gxfX45owL61
	QN2lnjT7I3IEyneMfynRnbrfql8e5XTjEBzsMrWeSrFPV/Nz5cBE/aSrVMFWfRwmmOKD
	Auyi+/I0lz6aXGo/YtQiLWSH4CqYmH3BetXz48O9rSUC+KQwSb2VJA2t8ajf7QtREmGT
	RoQIwACNpS7fAii0RC+MCvEE97nYt36Vtvp4TlQZUs9HO8/0nUfpb6HwPlk1EoUZTYOr
	ND8g==
X-Gm-Message-State: ALoCoQnMWpfzyH4qWEd85FVR2vWifqlFHkTKhxFHWfMoxpvGUt1cOYCuybxzGQ8YUHFNRmPko/88
MIME-Version: 1.0
X-Received: by 10.152.44.232 with SMTP id h8mr2068419lam.104.1440008537807;
	Wed, 19 Aug 2015 11:22:17 -0700 (PDT)
Received: by 10.25.15.22 with HTTP; Wed, 19 Aug 2015 11:22:17 -0700 (PDT)
In-Reply-To: <CADJgMzv+cKPY9wrAzbk5pgQJS0=R9KWu-+EuppM=nmXs8RHxYg@mail.gmail.com>
References: <CALqxMTFkgGx0FxMiZ77inOZSs_+TQ88Wpj-q-c12COkO9tP4gQ@mail.gmail.com>
	<CADJgMzv+cKPY9wrAzbk5pgQJS0=R9KWu-+EuppM=nmXs8RHxYg@mail.gmail.com>
Date: Wed, 19 Aug 2015 20:22:17 +0200
Message-ID: <CABm2gDrQ3DEDQLA0b6kTppxU+CL6rYNocymPeVo2eTmLnDUYLw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
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: Wed, 19 Aug 2015 18:22:20 -0000

On Wed, Aug 19, 2015 at 7:32 PM, Btc Drak via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Wed, Aug 19, 2015 at 5:53 PM, Adam Back via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> ignored the warnings.  Many also warned that 75% was an optimally BAD
>> trigger ratio (and that in a hard fork it is not a miner vote really
>> as in soft-forks).  Gavin & Mike ignored that warning to.  I know they
>> heard those warnings because I told them 1:1 in person or via email
>> and had on going conversations.  Others did too.
>
> I would like to add for the record, I also warned Gavin of this in his
> PR to Bitcoin Core, and also suggested a timeout which if
> activation/enforcement did not occur within, hard fork deployment
> would be cancelled. His response was to delete these from the PR
> claiming thresholds were not relevant conversation in his PR and
> belonged elsewhere (even though they had already been discussed
> elsewhere).

I don't know the timeline for this, but maybe he was referring to
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009731.html
(where he is one of the few people that have participated).