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
|
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 42513412
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 11 Jun 2017 13:17:45 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f43.google.com (mail-vk0-f43.google.com
[209.85.213.43])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 99C8E1D7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 11 Jun 2017 13:17:44 +0000 (UTC)
Received: by mail-vk0-f43.google.com with SMTP id g66so40474726vki.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 11 Jun 2017 06:17:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=n8YzR19Ra2l3rH7Xa3lSbG6cU91t1kJV3wYwQkDaYjg=;
b=V55Rv3BCCKF8xisY+L26eH9aomXEIxYROhJqoo5gmek8kCxVWGX/cFXs9hLkaJ89m4
nEbK4zF9jYU2vSKZxdWbPLOzMMCWGE3k3XS9zUDZRLY6QnJEXSnliDGmtKHsRn/s4WJK
CkS/9phnQCEHWt6h6MM0s1LvPYj2zUWu2N/1aVaLqex22bHUYKqtNZy4FpsmgtVOSInu
bCcIrwG4wAIQHTRjA39Q164Kbe93rYfpv0u1aME7JheK3//nVCbLCzm4D9N/3nOCE72L
3NcWnuQ3h5MtRbx+vWnRAjqRbHWu/MOu2VbitoLnptwuvn58nibajriHCpCeN2PSKqwf
mEdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=n8YzR19Ra2l3rH7Xa3lSbG6cU91t1kJV3wYwQkDaYjg=;
b=dPjAbb+y5S+r9X0HGip3hJ9D9H7gkm1tNGlsDGzr+9uIyiydddZihaxHZjuddcumUQ
WmOjlQmWaIQ6VYfDlm/NoqGjKxq9a2FGtS24GQdqborysM2LF5t3TlnTR8f/FOY5PwjD
dAQ9P4TiPSKb3LM+QFvbYNTAhqAtxyMKwGSs+/U1jWp1W0WVU71YbTRphPxDuG0uGMVE
E/XVjtai8sqVNqn1KYOpWtxgZBqQOrkpk1aLDGB6XTDi0ZM6Ow9a1bRfRMmsNG8bVz7m
TOJMjHrsi43JBs1iZHYBvpo/J3dX+dS5XsOqBPNWM4QqPtpatv6XrblcULNNRe5jaYLK
QDrQ==
X-Gm-Message-State: AODbwcBCI0r6wFhWDHtftOyldvjKWco4e9dqzo2j7J44IY+E1zJJ1ctA
Km3kWbYQKPkzuktILdlXu3c7BXkpNAAH
X-Received: by 10.31.9.204 with SMTP id 195mr26070642vkj.115.1497187063684;
Sun, 11 Jun 2017 06:17:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.52.213 with HTTP; Sun, 11 Jun 2017 06:17:43 -0700 (PDT)
In-Reply-To: <CAMnpzfqqmTFkf_HKPb18ijm-bYja_MpRofBYNXd3TkqVLsJhNw@mail.gmail.com>
References: <CAAS2fgQNPvEuta0KubeDetgYxGhWvdGK10jig0y4ayv0EvZPLw@mail.gmail.com>
<87r2ze2833.fsf@rustcorp.com.au>
<63d03825-da9b-328d-56b8-0d062f3e0c62@mattcorallo.com>
<87inkn14gq.fsf@rustcorp.com.au>
<CAMnpzfqqmTFkf_HKPb18ijm-bYja_MpRofBYNXd3TkqVLsJhNw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Sun, 11 Jun 2017 15:17:43 +0200
Message-ID: <CABm2gDqr=SHgva4H1sBtW_k8-5RxupSzq+zanmz21e=X2P=6Gg@mail.gmail.com>
To: Ryan Grant <bitcoin-dev@rgrant.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP149 timeout-- why so far in the future?
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, 11 Jun 2017 13:17:45 -0000
The current proposal assumes that bip149 would only be merged and
released after nov15, so there's not time in one day.
My preference would be a bip149 proposal that could be merged and
released now, but some people complain that would require more
testing, because if you deploy bip149 and then sw gets activated pre
nov15, then you want bip149 nodes to use the old service bit for
segwit, not the new one (you would use that one if it activates post
nov15, so that pre-bip149 nodes don't get confused).
I was slowly modifying shaolinfry's code to try to code that, but I'm
currently not working on it because there doesn't seem there's a lot
of interest in releasing bip149 before nov15...
https://github.com/jtimon/bitcoin/commits/b15-shaolinfry-bip149
On Sun, Jun 11, 2017 at 7:48 AM, Ryan Grant via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Is there any reason that BIP149 activation on November 16th would
> cause a problem?
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
