Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.177 as permitted sender)
	client-ip=209.85.223.177; envelope-from=ematiu@gmail.com;
	helo=mail-ie0-f177.google.com; 
MIME-Version: 1.0
Sender: ematiu@gmail.com
From: Matias Alejo Garcia <matias@bitpay.com>
Date: Fri, 13 Mar 2015 00:48:05 -0300
Message-ID: <CA+vKqYfG=SoNAgTeD0C_Q7F2p6MWdWE90u7728g9s3=nkmNi4w@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a113eb1526ce6ab0511235fa5
Subject: [Bitcoin-development] BIP32 Index Randomisation
Precedence: list

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

Hello everyone,

We are working on bitcore-wallet-server (BWS), a HD multisig wallet
'facilitator'. We have a couple of questions regarding BIP32 path usage,
and we would love to have feedback from you before moving forward.

Currently the BWS instances hold the set of extended public keys of the
wallet's peers to be able to derive  addresses.

Since this is a problem from the privacy point of view, we thought using
pseudo-random  BIP32 paths, with a seed only known be the peers, so the
server will be able to verify that addresses  submitted by peers belong to
the wallet, but will not be able to derive future wallet addresses.

The workflow would be something like:

```
Peer >   getCurrentIndex

< Server [index]

Peer:
  pathSeed =3D PRNG(seed, index);

Peer > createAddress(index, pathSeed);

Server:
  derives the address and add it to the wallet.

< Server  new address

Peer: Verifies the address and inform it the user.
```

This way, accessing server data won't reveal future wallet addresses. The
seed (only known by the peers) could
be derived from hashes of their xprivs, so wallet funds can still be
recover with:
  1) The complete set of xprivs
  2) The quorum of xprivs + the complete set of xpubs + the address seed.

Thanks a lot in advance for any comment on this schema.

mat=C3=ADas

--=20
BitPay.com

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

<div dir=3D"ltr"><div><br></div><div>Hello everyone,</div><div><br></div><d=
iv>We are working on bitcore-wallet-server (BWS), a HD multisig wallet &#39=
;facilitator&#39;. We have a couple of questions regarding BIP32 path usage=
, and we would love to have feedback from you before moving forward.</div><=
div><br></div><div>Currently the BWS instances hold the set of extended pub=
lic keys of the wallet&#39;s peers to be able to derive =C2=A0addresses.</d=
iv><div><br></div><div>Since this is a problem from the privacy point of vi=
ew, we thought using pseudo-random =C2=A0BIP32 paths, with a seed only know=
n be the peers, so the server will be able to verify that addresses =C2=A0s=
ubmitted by peers belong to the wallet, but will not be able to derive futu=
re wallet addresses.</div><div><br></div><div>The workflow would be somethi=
ng like:</div><div><br></div><div>```</div><div>Peer &gt; =C2=A0 getCurrent=
Index</div><div><br></div><div>&lt; Server [index]</div><div><br></div><div=
>Peer:</div><div>=C2=A0 pathSeed =3D PRNG(seed, index);</div><div><br></div=
><div>Peer &gt; createAddress(index, pathSeed);</div><div><br></div><div>Se=
rver:=C2=A0</div><div>=C2=A0 derives the address and add it to the wallet.<=
/div><div><br></div><div>&lt; Server =C2=A0new address</div><div><br></div>=
<div>Peer: Verifies the address and inform it the user.</div><div>```</div>=
<div><br></div><div>This way, accessing server data won&#39;t reveal future=
 wallet addresses. The seed (only known by the peers) could</div><div>be de=
rived from hashes of their xprivs, so wallet funds can still be recover wit=
h:</div><div>=C2=A0 1) The complete set of xprivs</div><div>=C2=A0 2) The q=
uorum of xprivs + the complete set of xpubs + the address seed.</div><div><=
br></div><div>Thanks a lot in advance for any comment on this schema.</div>=
<div><br></div><div>mat=C3=ADas</div><div><br></div>-- <br><div class=3D"gm=
ail_signature"><div dir=3D"ltr"><div>BitPay.com</div></div></div>
</div>

--001a113eb1526ce6ab0511235fa5--