MIME-Version: 1.0
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
Subject: Re: [bitcoin-dev] Start time for BIP141 (segwit)
Precedence: list

--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">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"=
_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</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"">&gt; It&#39;s not the website&#39;s fault if wallet devs a=
ren&#39;t updating their<br>
&gt; statuses. Besides, &quot;WIP&quot; 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&#39;ve made that hard part already (firwmare) so we know it is feasible=
, yet we didn&#39;t spend enough time on finalizing all the stack like our =
web wallet because we don&#39;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&#39;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&#39;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--