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>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list


--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--