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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
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 1WdiNf-0007Jp-6a
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 15:49:39 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.54 as permitted sender)
client-ip=209.85.219.54; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f54.google.com;
Received: from mail-oa0-f54.google.com ([209.85.219.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WdiNd-0003YI-Vg
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Apr 2014 15:49:39 +0000
Received: by mail-oa0-f54.google.com with SMTP id i7so4388275oag.41
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Apr 2014 08:49:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.229.228 with SMTP id st4mr7552351oec.16.1398440972516;
Fri, 25 Apr 2014 08:49:32 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Fri, 25 Apr 2014 08:49:32 -0700 (PDT)
In-Reply-To: <CAAS2fgRiXdOBN2gVZ0Xh4kBeOKiS80AjD5+VxJEut9nWt-0WUg@mail.gmail.com>
References: <ljdd29$522$1@ger.gmane.org>
<1398437607.23028.110362141.03111A2A@webmail.messagingengine.com>
<CAAS2fgRiXdOBN2gVZ0Xh4kBeOKiS80AjD5+VxJEut9nWt-0WUg@mail.gmail.com>
Date: Fri, 25 Apr 2014 17:49:32 +0200
X-Google-Sender-Auth: tEt_2Cx5dQe1LmLTxGX1DEjOBNY
Message-ID: <CANEZrP0+SBMpjnQwbspZ_A6ZA8GepwW9G98AZU2jfWHuGCtEHg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11362fb068043104f7dfe975
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: 1WdiNd-0003YI-Vg
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove
it?
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, 25 Apr 2014 15:49:39 -0000
--001a11362fb068043104f7dfe975
Content-Type: text/plain; charset=UTF-8
I generally agree, but I wonder how popular cloning wallets between devices
will be in future. Right now if someone wants to have a wallet shared
between Hive, blockchain.info and Bitcoin Wallet for Android, we just tell
them they're out of luck and they need to pick one, or split their funds up
manually.
But probably a lot of people would like to use different UI's to access the
same wallets. Sharing key trees is a part of that, though full blown wallet
metadata sync would also be needed.
So I guess we're going to end up with some kind of fairly complex
compatibility matrix. But I agree it may be unavoidable.
--001a11362fb068043104f7dfe975
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I generally agree, but I wonder how popular cloning wallet=
s between devices will be in future. Right now if someone wants to have a w=
allet shared between Hive, <a href=3D"http://blockchain.info">blockchain.in=
fo</a> and Bitcoin Wallet for Android, we just tell them they're out of=
luck and they need to pick one, or split their funds up manually.<div>
<br></div><div>But probably a lot of people would like to use different UI&=
#39;s to access the same wallets. Sharing key trees is a part of that, thou=
gh full blown wallet metadata sync would also be needed.</div><div><br>
</div><div>So I guess we're going to end up with some kind of fairly co=
mplex compatibility matrix. But I agree it may be unavoidable.</div></div>
--001a11362fb068043104f7dfe975--
|
