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
122
123
124
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1Wd3b1-0007Tz-Kp
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:16:43 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Wd3b0-0004TQ-95
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:16:43 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1Wd3at-0001iv-VJ; Wed, 23 Apr 2014 22:16:35 +0200
Content-Type: multipart/signed;
boundary="Apple-Mail=_BF3ED200-533E-4A91-ABE8-A01C91E64123";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <201404232009.08791.luke@dashjr.org>
Date: Wed, 23 Apr 2014 22:17:12 +0200
Message-Id: <34401F0D-FDB9-4C95-AC57-660DC3E5331B@bitsofproof.com>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<201404232001.06679.luke@dashjr.org> <53581CB3.2000109@gk2.sk>
<201404232009.08791.luke@dashjr.org>
To: Luke-Jr <luke@dashjr.org>
X-Mailer: Apple Mail (2.1874)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1398284202;
c5773f26;
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Wd3b0-0004TQ-95
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] New BIP32 structure
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: Wed, 23 Apr 2014 20:16:43 -0000
--Apple-Mail=_BF3ED200-533E-4A91-ABE8-A01C91E64123
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On 23.04.2014, at 22:09, Luke-Jr <luke@dashjr.org> wrote:
> On Wednesday, April 23, 2014 8:04:03 PM Pavol Rusnak wrote:
>> On 04/23/2014 10:01 PM, Luke-Jr wrote:
>>> Yes, it should scan all possible (under the BIP-defined structure)
>>> branches regardless of which features it supports.
>>=20
>> So you suggest to scan for accounts, show balances but don't allow =
user
>> to spend them? Does not seem right to me.
>=20
> Scan all branches for UTXOs, then you have the balance for the wallet. =
Account=20
> balances are metadata, so cannot be known from the seed alone. If you =
want to=20
> have a way to restore accounts, you must define some more detailed =
wallet file=20
> format (which could be built on top of this).
>=20
> On Wednesday, April 23, 2014 8:04:35 PM you wrote:
>> On 23.04.2014, at 22:02, Luke-Jr <luke@dashjr.org> wrote:
>>> On Wednesday, April 23, 2014 8:01:16 PM Tamas Blummer wrote:
>>>> The wallet has to know how it got the UTXO in order to be able to =
spend
>>>> it.
>>>=20
>>> No it doesn't... Just the assigned scriptPubKey and secret(s) =
required to
>>> satisfy it.
>>=20
>> To know the secret it needs to know which key coordinate to use that =
is
>> logically the same as knowing the address it used to receive it.
>=20
> Sure, it *knows* what address was used to receive it. But at the point =
it's a=20
> UTXO, that address is no longer relevant.
>=20
In context of BIP32 one does not store secrets but re-create them =
on-the-fly if needed using key coordinates known to the UTXO.
Individual secrets per UTXO are about as irrelevant and accessible as =
addresses.
--Apple-Mail=_BF3ED200-533E-4A91-ABE8-A01C91E64123
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTWB/IAAoJEPZykcUXcTkchL4H/Rz6q+OdD2+ZruWjs/A3jEpW
jwye8ysIa9sMkcSKYs8PhIpyWHmzcxpNNNWvOVb22q/vEE6/537wZ91SdqCpVHLB
pfv4bJzh45U3w0x+ytsAjvS81J193x7k8je2OIYmbTwKTwce640JOBW1EG/fTnXU
paPcIwPXGhi9sOitikseqw8q+sRdL73ZovL92j/K8pqdIAc00RAxuQz7/JmYDMe1
Kq1gsO2MfZXrumKAhUt346eXAhg6Xrcxbr7jeY8DI75ADNCdxQ0G45s8g1Nx3wfZ
Ubmig02BHpG2OCMbusitp9IfckCPZ+OH5L6KuT2DkInY2yYW0GPlQlrR7MYVw5w=
=O3I9
-----END PGP SIGNATURE-----
--Apple-Mail=_BF3ED200-533E-4A91-ABE8-A01C91E64123--
|
