1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YWXE8-00060x-45
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Mar 2015 21:34:40 +0000
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;
Received: from mail-ie0-f172.google.com ([209.85.223.172])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YWXE7-0000hz-3f
for bitcoin-development@lists.sourceforge.net;
Fri, 13 Mar 2015 21:34:40 +0000
Received: by iecvj10 with SMTP id vj10so123757476iec.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 13 Mar 2015 14:34:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.247.68 with SMTP id mb4mr60460830icb.2.1426282471625;
Fri, 13 Mar 2015 14:34:31 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.36.54.147 with HTTP; Fri, 13 Mar 2015 14:34:31 -0700 (PDT)
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
X-Google-Sender-Auth: 6e1idFZycopBElpfzTLdSLCrsGg
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
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YWXE7-0000hz-3f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 Index Randomisation
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2015 21:34:40 -0000
--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'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'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's worth the additional co=
mplexity is something I don't have any feedback on, only you can judge =
that.</div></div><br></div></div>
--90e6ba1ef2ea125233051132447a--
|
