MIME-Version: 1.0
In-Reply-To: <D36DB0BD-C805-4346-B425-77D5B29582E5@gmail.com>
References: <8F096BE1-D305-43D4-AF10-2CC48837B14F@gmail.com>
	<20170225010122.GA10233@savin.petertodd.org>
	<208F93FE-B7C8-46BE-8E00-52DBD0F43415@gmail.com>
	<CAN6UTayzQRowtWhLKr8LyFuXjw3m+GjQGtHfkDj-Xu41Hym32w@mail.gmail.com>
	<CAEM=y+WkgSkc07ZsU6APAkcu37zVZ7dwSc=jAg1nho31S5ZyxQ@mail.gmail.com>
	<20170225191201.GA15472@savin.petertodd.org>
	<CAMZUoK=sq_sRoXuySca-VAGwA3AzeoZ5iNFSnKULbj+NtPjHFA@mail.gmail.com>
	<20170225210406.GA16196@savin.petertodd.org>
	<CAGLBAhdCb+QLWRm4FWkPvaM2sU24HuafdgNiS=wgnPTGzrW05w@mail.gmail.com>
	<4FE38F6A-0560-4989-9C53-7F8C94EA4C76@gmail.com>
	<20170225214018.GA16524@savin.petertodd.org>
	<D36DB0BD-C805-4346-B425-77D5B29582E5@gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
Date: Sat, 25 Feb 2017 14:14:44 -0800
Message-ID: <CAPg+sBhZ1UqOLqz_PVjjrE8Cbte_Y160Gq7P7EWf6cRKjMcDEQ@mail.gmail.com>
To: Steve Davis <steven.charles.davis@gmail.com>, 
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11436b6e77d9bd0549622cb7
Subject: Re: [bitcoin-dev] SHA1 collisions make Git vulnerable to attakcs by
 third-parties, not just repo maintainers
Precedence: list

--001a11436b6e77d9bd0549622cb7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Feb 25, 2017 14:09, "Steve Davis via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

Hi Peter,


I really, really don=E2=80=99t want to get into it but segwit has many aspe=
cts that
are less appealing, not least of which being the amount of time it would
take to reach the critical mass.

Surely there's a number of alternative approaches which could be explored,
even if only to make a fair assessment of a best response?


Any alternative to move us away from RIPEMD160 would require:
* A drafting of a softfork proposal, implementation, testing, review.
* A new address format
* Miners accepting the new consensus rules
* Wallets adopting the new address format, both on the sender side and
receiver side (which requires new signatures).

I.e., exactly the same as segwit, for which most of these are already done.
And it would still only apply to wallets adopting it.

--=20
Pieter

--001a11436b6e77d9bd0549622cb7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Feb 25, 2017 14:09, &quot;Steve Davis via bitcoin-dev&quot; &l=
t;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@list=
s.linuxfoundation.org</a>&gt; wrote:<br type=3D"attribution"><blockquote cl=
ass=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Hi Peter,<br>
<div class=3D"quoted-text"><br></div><div class=3D"quoted-text">
<br>
</div>I really, really don=E2=80=99t want to get into it but segwit has man=
y aspects that are less appealing, not least of which being the amount of t=
ime it would take to reach the critical mass.<br>
<br>
Surely there&#39;s a number of alternative approaches which could be explor=
ed, even if only to make a fair assessment of a best response?<br></blockqu=
ote></div></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Any alt=
ernative to move us away from RIPEMD160 would require:</div><div dir=3D"aut=
o">* A drafting of a softfork proposal, implementation, testing, review.</d=
iv><div dir=3D"auto">* A new address format</div><div dir=3D"auto">* Miners=
 accepting the new consensus rules</div><div dir=3D"auto">* Wallets adoptin=
g the new address format, both on the sender side and receiver side (which =
requires new signatures).</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">I.e., exactly the same as segwit, for which most of these are already don=
e. And it would still only apply to wallets adopting it.</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">--=C2=A0</div><div dir=3D"auto">Pieter</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></di=
v></div></div>

--001a11436b6e77d9bd0549622cb7--