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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
Return-Path: <joroark@vt.edu>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 49F96955
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 17:48:51 +0000 (UTC)
X-Greylist: delayed 01:00:48 by SQLgrey-1.7.6
Received: from omr1.cc.vt.edu (outbound.smtp.vt.edu [198.82.183.121])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 74C29A5
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 17:48:50 +0000 (UTC)
Received: from mr1.cc.vt.edu (mail.ipv6.vt.edu
[IPv6:2607:b400:92:9:0:9d:8fcb:4116])
by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id u9GGm16L024575
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 12:48:01 -0400
Received: from mail-pa0-f70.google.com (mail-pa0-f70.google.com
[209.85.220.70])
by mr1.cc.vt.edu (8.14.7/8.14.7) with ESMTP id u9GGltC7018434
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 12:48:00 -0400
Received: by mail-pa0-f70.google.com with SMTP id ry6so172937870pac.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 09:48:00 -0700 (PDT)
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;
bh=tAqzthZr/Jd7Xcaf1/7Rgb98+gYeIS2jdRvD6qMoJTA=;
b=Hxm21o6vT2AMw3DmKO0l72uoffuI4SlAnWQ0sz4BllgcKAQHD/Z0MpRftvjg5Skyxt
1dGBuXP5HuyNrtRAfw+k/BN53OVUcpdjAV3mYi/VehhuWyKffzlkcO65qZh2+Zok5vPD
c0zGhq9IwfDyQOiERwFOKQk8ot36V/OBAXI0idNKptfi/2gciw7xzi9yYSqZWvwRLDOw
NiQ1ZqKCMxl2H93M/wjY/K95/vk+MYn1O5Y/N+iwhZb3kDRPWAlNoncMVj1us9iQtzaq
aVNGAK2NOT6gMAxqtKy9ZCnPpm5cw5A+3vZI9GONHFYS1mgKDhaGFJez8gJoh/iz13Vz
QB1g==
X-Gm-Message-State: AA6/9RmI6ZeDN8VUjWFlB3QOg11g0htieMx6L8lqx/pKp2BiB1YI/aLpTOByXnx/CG0KawCRiaplTuuJn4UyvjmtIdKR7UUUHCGpfwoLjhoc7LFP1/HPwSJsE8eTtnHKcLP1T0jnW/m7CJb/KNyfZL5UlLtcOvSUBp1nuiGHACzUCdQ1Zf8ZG/S0ezc1v/blgZIHs4/F5oyuo3YFmqzWvxE=
X-Received: by 10.66.222.5 with SMTP id qi5mr26137670pac.138.1476636475239;
Sun, 16 Oct 2016 09:47:55 -0700 (PDT)
X-Received: by 10.66.222.5 with SMTP id qi5mr26137653pac.138.1476636475018;
Sun, 16 Oct 2016 09:47:55 -0700 (PDT)
Received: from Doug-Armory.local ([172.56.39.104])
by smtp.googlemail.com with ESMTPSA id
sv8sm41856829pab.18.2016.10.16.09.47.54
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sun, 16 Oct 2016 09:47:54 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAPg+sBjdyJ297-GZvVc-wQwCEX-cRAGTNWDd92SgVzdCcD_ZMw@mail.gmail.com>
<1782741.nelbyupFSb@strawberry>
<CABsx9T2sWKFKpRYsjcgcdef+nL7X9-4+3H10hAy1FsXaax38Og@mail.gmail.com>
From: Douglas Roark <joroark@vt.edu>
Message-ID: <2d5abad7-cd9d-4396-4dd2-c687a1a808dc@vt.edu>
Date: Sun, 16 Oct 2016 09:47:40 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABsx9T2sWKFKpRYsjcgcdef+nL7X9-4+3H10hAy1FsXaax38Og@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="9b8bgSx0K8MHugXqsfI8SMUocIWopeNGG"
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD 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 17:48:51 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9b8bgSx0K8MHugXqsfI8SMUocIWopeNGG
Content-Type: multipart/mixed; boundary="Ma2J567GI6FEpNhjntlW90AR6W5v819Wl";
protected-headers="v1"
From: Douglas Roark <joroark@vt.edu>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <2d5abad7-cd9d-4396-4dd2-c687a1a808dc@vt.edu>
Subject: Re: [bitcoin-dev] Start time for BIP141 (segwit)
References: <CAPg+sBjdyJ297-GZvVc-wQwCEX-cRAGTNWDd92SgVzdCcD_ZMw@mail.gmail.com>
<1782741.nelbyupFSb@strawberry>
<CABsx9T2sWKFKpRYsjcgcdef+nL7X9-4+3H10hAy1FsXaax38Og@mail.gmail.com>
In-Reply-To: <CABsx9T2sWKFKpRYsjcgcdef+nL7X9-4+3H10hAy1FsXaax38Og@mail.gmail.com>
--Ma2J567GI6FEpNhjntlW90AR6W5v819Wl
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On 2016/10/16 09:35, Gavin Andresen via bitcoin-dev wrote:
> I asked a lot of businesses and individuals how long it would take them=
> to upgrade to a new release over the last year or two.
>=20
> Nobody said it would take them more than two weeks.
>=20
> If somebody is running their own validation code... then we should
> assume they're sophisticated enough to figure out how to mitigate any
> risks associated with segwit activation on their own.
In addition, there has been a page up for several months
(https://bitcoincore.org/en/segwit_adoption/) that gauges whether or not
wallets are ready for SegWit. Unfortunately, it appears that the page
hasn't been updated since May. I do know that several wallets have
finished or are close to finishing their support, though.
Would I want anyone to lose money due to faulty wallets? Of course not.
By the same token, devs have had almost a year to tinker with SegWit and
make sure the wallet isn't so poorly written that it'll flame out when
SegWit comes along. It's not like this is some untested, mostly unknown
feature that's being slipped out at the last minute, unlike other
features I could name but won't. :)
--=20
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt.edu
PGP key ID: 26623924
--Ma2J567GI6FEpNhjntlW90AR6W5v819Wl--
--9b8bgSx0K8MHugXqsfI8SMUocIWopeNGG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYA686AAoJEEOBHRomYjkkHwgP/3/0EDDIUagqFHp9K9ZaROGX
2VuBVB5BYhgwwsaVLvjlJoi0ljkWQ5e91QWPe3bi4Ul+t6C4ENt/Ppr2ZjRHmjMk
wYt8o9AwdR/IFeWlnKlDQ0pHNFBm10Pq1Oyd/qNjXY4Z0q5qAqW3+n1Dtm1Z/2xw
/XTi8JtGGFv+oGNo3aVRl/NQJQ8JZRsJwUMa5bstK6zV+fIBDiA7z7WEkSy9w/VQ
kTwAsWUoCaAR6agDDhpN0OlGHl+MZmtpGep8MaPNIDKD7RRA3x69K9YeRHI46nqY
WrCCKSYRRkcTrD7VB+mFcfqrvxIyoAXgKPAKvAF4Y4ld0rjPKntUOxPnJv296nu5
18LKCms7TBIUqEyWZDsOGnoKXfOwqFJlqun0wjVTjl8zU8r0oUrGEcQD+Gz2/89g
yS0GVNJ/I5MbgGpVrMxaYg4Ad4aIMC3b8IY5MncMg0kQeGzgFrGb6A2tp4YfmA3/
PT17C0EWSOoXrXHxDgEdrZH9xbgX1Lm8IJg5WTYVAUHjEC0Hvrl7YEQGtJC4z3e3
OyjlxvdGmY5CSrT9+frUIOIH1TZRpBG+uJJuT5JxPoWCht0TTq0/MyWnFgTF6sn8
2pqxZBkIBWQMbpSGB218KQyhodohjZoKIMp5Sh+Ap+ba/YjtaEaFzYi28NBOUaJT
VKLtgM40uK8OvcUKGRNa
=+Z3E
-----END PGP SIGNATURE-----
--9b8bgSx0K8MHugXqsfI8SMUocIWopeNGG--
|
