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: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B2EFDA67
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 19:11:32 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sender163-mail.zoho.com (sender163-mail.zoho.com
[74.201.84.163])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EFA9510F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 19:11:31 +0000 (UTC)
Received: from mail.zoho.com by mx.zohomail.com
with SMTP id 1476645083235143.39714122433338;
Sun, 16 Oct 2016 12:11:23 -0700 (PDT)
Date: Mon, 17 Oct 2016 03:11:23 +0800
From: Johnson Lau <jl2012@xbt.hk>
To: "Tom Zander" <tomz@freedommail.ch>,
"bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <157cee7d85f.d54d998f341542.5677728872543901935@xbt.hk>
In-Reply-To: <9782389.Gd5V7OpbDZ@strawberry>
References: <CAPg+sBjdyJ297-GZvVc-wQwCEX-cRAGTNWDd92SgVzdCcD_ZMw@mail.gmail.com>
<2034434.4WpKWoeOrB@strawberry>
<CABm2gDrhCw-5mpCK814hK4Y1sEUcHZyFMHqHziC1b1LLtMWVDA@mail.gmail.com>
<9782389.Gd5V7OpbDZ@strawberry>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
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 19:11:32 -0000
---- On Mon, 17 Oct 2016 02:54:04 +0800 Tom Zander via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote ----
> Honestly, if the reason for the too-short-for-safety timespan is that you
> want to use BIP9, then please take a step back and realize that SegWit is a
> contriversial soft-fork that needs to be deployed in a way that is extra
> safe because you can't roll the feature back a week after deployment.
> All transactions that were made in the mean time turn into everyone-can-
> spent transactions.
No one should use, nor anyone is advised to use, segwit transactions before it is fully activated. Having 2 months or 2 weeks of grace period makes totally no difference in this regard. If anyone tried to use segwit tx during your proposed 2 months grace period, all those txs were still everyone-can-spent.
All you are advocating is just stalling the process with no improvement in security.
>
> I stand by the minimum of 2 months. There is no reason to use BIP9 as it was
> coded in an older client. That is an excuse that I don't buy.
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
|
