Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.172 as permitted sender)
	client-ip=209.85.223.172; envelope-from=mh.in.england@gmail.com;
	helo=mail-ie0-f172.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CA+vKqYeafvwJkwWfiMTZDhO_7nxbdLFRppptZRbRoeBJP8O9qg@mail.gmail.com>
References: <CA+vKqYfG=SoNAgTeD0C_Q7F2p6MWdWE90u7728g9s3=nkmNi4w@mail.gmail.com>
	<CANEZrP0t0oXGz6uXaLrGHFKUeRNFBC_MKr7x3uTH3WPkTbe5tQ@mail.gmail.com>
	<CA+vKqYfNLvuQH2CEcgvJqPPOYg=1M6=1sTPm65xec7vdzTgP_A@mail.gmail.com>
	<CANEZrP1a_hqkZSfnWbfzJj2Y7Z0yptUOuH5iFG=CB5hwjWG3Ew@mail.gmail.com>
	<CA+vKqYeafvwJkwWfiMTZDhO_7nxbdLFRppptZRbRoeBJP8O9qg@mail.gmail.com>
Date: Fri, 13 Mar 2015 14:34:31 -0700
Message-ID: <CANEZrP2E5p+oK1WHC=ZdvqFCo7Cwqrf0NXUCKJ9TPn3wdLBY-Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matias Alejo Garcia <matias@bitpay.com>
Content-Type: multipart/alternative; boundary=90e6ba1ef2ea125233051132447a
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 Index Randomisation
Precedence: list

--90e6ba1ef2ea125233051132447a
Content-Type: text/plain; charset=UTF-8

>
> You are killing us Mike! :) We really don't like to think that BWS is
> a webwallet. Note
> that private keys are not stored (not even encrypted) at the server.


Sure, sorry, by web wallet I meant a blockchain.info/CoPay type setup where
the client has the private keys and signs txns, but otherwise relies on the
server for learning about the wallet contents. I tend to call wallets where
the server has the private key BitBanks but I don't know if anyone else
uses this terminology. It might just be a personal quirk of my own ;)


> we think having some visibility of the wallet by the multisig
> facilitator will make the user experience much better (e.g: mobile
> notifications).
>

Fair enough. Yes, push notifications to mobiles in a decentralised way is
rather a hard problem.

I think what Gregory suggested is then the best approach for you to do what
you want. Whether it's worth the additional complexity is something I don't
have any feedback on, only you can judge that.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">You are killing us Mike! :) We really don&#39;t =
like to think that BWS is<br>
a webwallet. Note<br>
that private keys are not stored (not even encrypted) at the server. </bloc=
kquote><div><br></div><div>Sure, sorry, by web wallet I meant a <a href=3D"=
http://blockchain.info/CoPay">blockchain.info/CoPay</a> type setup where th=
e client has the private keys and signs txns, but otherwise relies on the s=
erver for learning about the wallet contents. I tend to call wallets where =
the server has the private key BitBanks but I don&#39;t know if anyone else=
 uses this terminology. It might just be a personal quirk of my own ;)</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">we think having some visib=
ility of the wallet by the multisig<br>
facilitator will make the user experience much better (e.g: mobile<br>
notifications).<br></blockquote><div><br></div><div>Fair enough. Yes, push =
notifications to mobiles in a decentralised way is rather a hard problem.</=
div><div><br></div><div>I think what Gregory suggested is then the best app=
roach for you to do what you want. Whether it&#39;s worth the additional co=
mplexity is something I don&#39;t have any feedback on, only you can judge =
that.</div></div><br></div></div>

--90e6ba1ef2ea125233051132447a--