MIME-Version: 1.0
In-Reply-To: <84f4a4b8-fcbd-433b-9556-174ec5475f61@satoshilabs.com>
References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>
	<8b4831a4-791e-c03e-baa4-16d9e5ead442@electrum.org>
	<84f4a4b8-fcbd-433b-9556-174ec5475f61@satoshilabs.com>
From: Kabuto Samourai <kabuto@samouraiwallet.com>
Date: Thu, 7 Sep 2017 11:33:09 -0500
Message-ID: <CA+_kfXLjeQJbJGy5=ssynGOTaGkzvzWQ2RMdhcqCG1DNjqvFWA@mail.gmail.com>
To: Pavol Rusnak <stick@satoshilabs.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f403045f78e0790a8b05589c063e"
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for
	BIP-32 wallets
Precedence: list

--f403045f78e0790a8b05589c063e
Content-Type: text/plain; charset="UTF-8"

OutputType byte solution is nearly equivalent to {x,y,z} and adds redundant
data. Implementations could erroneously (maliciously) assign the wrong
output type for the given purpose field.

We could reduce the scope of this improvement to BIP43, as suggested by
Thomas. BIP32-generic wallets may implement something else.

On Thu, Sep 7, 2017 at 11:23 AM, Pavol Rusnak via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On 07/09/17 06:29, Thomas Voegtlin via bitcoin-dev wrote:
> > A solution is still needed to wallets who do not wish to use BIP43
>
> What if we added another byte field OutputType for wallets that do not
> follow BIP43?
>
> 0x00 - P2PKH output type
> 0x01 - P2WPKH-in-P2SH output type
> 0x02 - native Segwit output type
>
> Would that work for you?
>
> The question is whether this field should be present only if depth==0x00
> or at all times. What is your suggestion, Thomas?
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


-- 
-Kabuto

PGP Fingerprint: 1A83 4A96 EDE7 E286 2C5A  B065 320F B934 A79B 6A99

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

<div dir=3D"ltr">OutputType byte solution is nearly equivalent to {x,y,z} a=
nd adds redundant data. Implementations could erroneously (maliciously) ass=
ign the wrong output type for the given purpose field.<div><br></div><div>W=
e could reduce the scope of this improvement to BIP43, as suggested by Thom=
as. BIP32-generic wallets may implement something else.</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Sep 7, 2017 at 11=
:23 AM, Pavol Rusnak via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@list=
s.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><span class=3D"">On 07/09/17 06:29, Thomas Voegtlin via bitcoin-dev wrot=
e:<br>
&gt; A solution is still needed to wallets who do not wish to use BIP43<br>
<br>
</span>What if we added another byte field OutputType for wallets that do n=
ot<br>
follow BIP43?<br>
<br>
0x00 - P2PKH output type<br>
0x01 - P2WPKH-in-P2SH output type<br>
0x02 - native Segwit output type<br>
<br>
Would that work for you?<br>
<br>
The question is whether this field should be present only if depth=3D=3D0x0=
0<br>
or at all times. What is your suggestion, Thomas?<br>
<span class=3D"im HOEnZb"><br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol &quot;stick&quot; Rusnak<br>
CTO, SatoshiLabs<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">____________________________=
__<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr"><div><div dir=3D"ltr">-Kabuto</div><div dir=3D"ltr"><br></div><div=
><font size=3D"1">PGP Fingerprint:=C2=A01A83 4A96 EDE7 E286 2C5A =C2=A0B065=
 320F B934 A79B 6A99</font></div></div></div></div>
</div>

--f403045f78e0790a8b05589c063e--