summaryrefslogtreecommitdiff
path: root/37/d8b307580b25d59dd44652d0eba2d93e63b635
blob: fdb41329f88c74389c6e9628624be98de6ea7d62 (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
Return-Path: <achow101@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 31F23A8C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 16 Oct 2016 21:18:49 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com
	[209.85.220.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B7259143
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 16 Oct 2016 21:18:48 +0000 (UTC)
Received: by mail-qk0-f174.google.com with SMTP id z190so205338083qkc.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 16 Oct 2016 14:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-transfer-encoding;
	bh=uSLXBxuPQ+4voBHt7sJpNkXrcUrCLPhbR6aNvoWaa4M=;
	b=SyY6jqVVIxbYsPmc0iFenGwLe0v2Sk4SmmTEEZ3gRSvz5+rLB1EUzK08DE4gXkiNav
	y+Ur2+hBXsXODHBiYc6P8dUlwvezc4qDBJJttPoQ1Y7hjip0OM/JXTNTlT05W3EAW9f0
	kyodoFUIneHLtxGId/78lcXN1RvRVnq4IVSUU1LMFSAhmrJFR0jeDYmc+g8P38djV6cJ
	mySQHwgBtzMBRPWOicod7NlFYeKEfn0DcPyiAbzO5CfGmgNh1J9pqBUGiSotFBQKqxgt
	tqrI2AxCbmrBRYmpipGiK4L56WqcoTiGPlvUsPsk6qFoAQFe86B1jE+xe7r/WrnFzzph
	Inog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-transfer-encoding;
	bh=uSLXBxuPQ+4voBHt7sJpNkXrcUrCLPhbR6aNvoWaa4M=;
	b=MfagKBRiPC48Fsx93HcxVuGhgKVTfSw3w20HWg1ncuV6HHLtKRxFHfmOv6SYQoH+LD
	wezW6Acc2TLZj7qAdQxzaoUEAR0OldNa2bm3PIRCpEaSIQv6mEjSisDZbX49ffiNakg6
	FiBY3JbQmGhIzYYBBkLdH1EgITOVFV7zVunjiYElG90R1rP7vBHX3MtXQUdC/IWSfDln
	ISZUEpqMfxEdZtZOIzNQ9e2gRLtAxsJLrglBBfVRhW0pIVOHEGGkFgeWs8gpMWMtXduC
	NOQ6Ji6RGUwbBnUE9km4uHWWZtww+tt0GsakEtuZpOk0ou1/MXsRHa2lwzPeUuRpUxd7
	tCkA==
X-Gm-Message-State: AA6/9RnhpNtO24HR1pd5AHzSdmZ3pDaq/USpaiXX4K6ix8Ffql+KD5bklodZ6Ss/vcP0hA==
X-Received: by 10.55.165.87 with SMTP id o84mr24391427qke.320.1476652728034;
	Sun, 16 Oct 2016 14:18:48 -0700 (PDT)
Received: from [192.168.1.6] (129-2-207-18.student.umd.edu. [129.2.207.18])
	by smtp.gmail.com with ESMTPSA id
	g11sm13341151qtb.19.2016.10.16.14.18.47
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Sun, 16 Oct 2016 14:18:47 -0700 (PDT)
To: Tom Zander <tomz@freedommail.ch>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <CAPg+sBjdyJ297-GZvVc-wQwCEX-cRAGTNWDd92SgVzdCcD_ZMw@mail.gmail.com>
	<2034434.4WpKWoeOrB@strawberry>
	<03831fcd-1fd5-b769-0b3b-41e996894e1f@vt.edu>
	<7939356.11nSWPlGYM@strawberry>
From: Andrew C <achow101@gmail.com>
Message-ID: <22046ac7-df36-2e2a-759e-b3dd01601c59@gmail.com>
Date: Sun, 16 Oct 2016 17:19:37 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
	Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7939356.11nSWPlGYM@strawberry>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM 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] Start time for BIP141 (segwit)
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: Sun, 16 Oct 2016 21:18:49 -0000



On 10/16/2016 4:58 PM, Tom Zander via bitcoin-dev wrote:
> Lets get back to the topic. Having a longer fallow period is a simple way to 
> be safe.  Your comments make me even more scared that safety is not taken 
> into account the way it would.

Can you please explain how having a longer grace period makes it any
safer? Once the fork reaches the LOCKED_IN status, the fork will become
active after the period is over. How does having a longer grace period
make this any safer besides just adding more waiting before it goes
active? You said something about rolling back the changes. There is no
mechanism for roll backs, and the whole point of the soft fork
signalling is such that there is no need to roll back anything because
miners have signaled that they are supporting the fork.