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
|
Return-Path: <marek@palatinus.cz>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3548C982
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 21:08:41 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com
[209.85.215.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5C53E13C
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 21:08:40 +0000 (UTC)
Received: by mail-lf0-f49.google.com with SMTP id l131so209230568lfl.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 14:08:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=palatinus-cz.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=xcMbjKijRqFNJ+SSz+yfSXTTvol1KWslxtvu4yAyp+M=;
b=124CB/ukCFWKi+CQdPyi2PGjto8P/WzPgIiVrFNCjO6oAuGIglxAm805VYnM6HRKUQ
z+9MRq64ehF9sjEKUTwOTDCxvGMoVTS9/aairZrepwxZBstQx389JuYErsONVkaMk8hO
BkOhNtuUkHNIGxwS3Gy0Q5d+TtlpMsL/R1XKyaJH+2WDU6BbH/oe3mNp9TXpckhzTmP3
k8l4BAfSAmQMgXYUmQztc+FpMq9ILW0j2g7JqO5e7WejRtvKOrPjaToMyZYX1jvB3blh
2lWPCdjWDnsDagSaHe0pHsk2mKjn4T89rNXKl5cEzFPl5ZPsPhI9f5ydPb/CxJdaT1Jt
IK2Q==
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:from:date
:message-id:subject:to;
bh=xcMbjKijRqFNJ+SSz+yfSXTTvol1KWslxtvu4yAyp+M=;
b=a1UyYBgAfy5bqZbQqBYy2ZhQqNvmBxBSIC7LtZqMtopriA8tYXO7KAiDdP1yHAsfNo
EzUAqEnqkxuSXav7Pm8WACVSNFSmC4AO5bcCJUWbOiYmxF7TrDg3b4oJDNOr8orbn+O9
xfzNRCTDWCpI2skFxb/PmvibegiG2ROIC6LCMbsePXDFYLnt27JG4BSVpcA/MKwl6gln
+jWG/kZYAZ7GS5RK7qQiL/omBjk0Zw0SIPPsTrDWvTYT9vm2vuIwpU7O3TSa96OmroMp
oknCq/ALGjgeDbG3eHlpGL8ebl4HZd7yaZAix94IzJwqrtSuJ2ItkoZyZgEKmvWxDvfg
GKsA==
X-Gm-Message-State: AA6/9RmV1RMc25Yg3PZYBVAVrsbPa7vWwbaVMwfChr6O2m9McANssJP19F+9s/xxyu5u1hi8ewU+YaMPa2ug+w==
X-Received: by 10.195.17.165 with SMTP id gf5mr9123189wjd.114.1476652118588;
Sun, 16 Oct 2016 14:08:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.43.135 with HTTP; Sun, 16 Oct 2016 14:08:08 -0700 (PDT)
In-Reply-To: <7939356.11nSWPlGYM@strawberry>
References: <CAPg+sBjdyJ297-GZvVc-wQwCEX-cRAGTNWDd92SgVzdCcD_ZMw@mail.gmail.com>
<2034434.4WpKWoeOrB@strawberry>
<03831fcd-1fd5-b769-0b3b-41e996894e1f@vt.edu>
<7939356.11nSWPlGYM@strawberry>
From: Marek Palatinus <marek@palatinus.cz>
Date: Sun, 16 Oct 2016 23:08:08 +0200
Message-ID: <CAJna-Hh8qoxv0n7XrfJ2-p_K1qDErr=dzakik2vAPcV-+-MYOw@mail.gmail.com>
To: Tom Zander <tomz@freedommail.ch>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=089e01681cdcfc58a8053f01dcab
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, HTML_MESSAGE, 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:08:41 -0000
--089e01681cdcfc58a8053f01dcab
Content-Type: text/plain; charset=UTF-8
On Sun, Oct 16, 2016 at 10:58 PM, Tom Zander via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Sunday, 16 October 2016 12:49:47 CEST Douglas Roark via bitcoin-dev
> wrote:
> > It's not the website's fault if wallet devs aren't updating their
> > statuses. Besides, "WIP" can mean an awful lot of things.
>
> As I said, it would be nice to get an updated version so we can see more
> than 20% readyness of wallets.
> The wallet devs not caring enough to update the status should be a worrying
> sign, though.
>
WIP for TREZOR means that we've made that hard part already (firwmare) so
we know it is feasible, yet we didn't spend enough time on finalizing all
the stack like our web wallet because we don't see any actual release date
yet. Considering current battles on BU hashpower, we decided simply sit and
watch (I already have popocorn).
SegWit is probably the most disruptive and most invasive change ever made to
> Bitcoin. We have miners actively saying they don't like it and this makes
> it
> a contriversial upgrade which means the network may split and other issues.
>
>
There're also many wallets which are impatiently waiting for segwit to be
released. Segwit is blessing for hardware wallets for many reasons. I
actually think that rolling out Segwit will increase security, because it
will reduce huge complexity in hardware wallets as it is today.
Slush
--089e01681cdcfc58a8053f01dcab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sun, Oct 16, 2016 at 10:58 PM, Tom Zander via bitcoin-dev <span dir=3D"l=
tr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"=
_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">On Sunday, 16 October 2016 12:49:47 CEST Douglas=
Roark via bitcoin-dev<br>
wrote:<br>
<span class=3D"">> It's not the website's fault if wallet devs a=
ren't updating their<br>
> statuses. Besides, "WIP" can mean an awful lot of things.<br=
>
<br>
</span>As I said, it would be nice to get an updated version so we can see =
more<br>
than 20% readyness of wallets.<br>
The wallet devs not caring enough to update the status should be a worrying=
<br>
sign, though.<br></blockquote><div><br></div><div>WIP for TREZOR means that=
we've made that hard part already (firwmare) so we know it is feasible=
, yet we didn't spend enough time on finalizing all the stack like our =
web wallet because we don't see any actual release date yet. Considerin=
g current battles on BU hashpower, we decided simply sit and watch (I alrea=
dy have popocorn).</div><div>=C2=A0</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">SegWit is probably the most disruptive and most invasive chan=
ge ever made to<br>
Bitcoin. We have miners actively saying they don't like it and this mak=
es it<br>
a contriversial upgrade which means the network may split and other issues.=
<br>
<br></blockquote><div><br></div><div>There're also many wallets which a=
re impatiently waiting for segwit to be released. Segwit is blessing for ha=
rdware wallets for many reasons. I actually think that rolling out Segwit w=
ill increase security, because it will reduce huge complexity in hardware w=
allets as it is today.</div><div>=C2=A0</div><div>Slush</div></div></div></=
div>
--089e01681cdcfc58a8053f01dcab--
|
