From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd3To-0002DL-E1 for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:09:16 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Wd3Tn-000212-CC for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:09:16 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:be5f:f4ff:febf:4f76]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id A000A108039D; Wed, 23 Apr 2014 20:09:45 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Wed, 23 Apr 2014 20:09:07 +0000 User-Agent: KMail/1.13.7 (Linux/3.12.6-gentoo; KDE/4.11.5; x86_64; ; ) References: <201404232001.06679.luke@dashjr.org> <53581CB3.2000109@gk2.sk> In-Reply-To: <53581CB3.2000109@gk2.sk> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201404232009.08791.luke@dashjr.org> X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Wd3Tn-000212-CC Subject: Re: [Bitcoin-development] New BIP32 structure X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2014 20:09:16 -0000 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. > > So you suggest to scan for accounts, show balances but don't allow user > to spend them? Does not seem right to me. Scan all branches for UTXOs, then you have the balance for the wallet. Account balances are metadata, so cannot be known from the seed alone. If you want to have a way to restore accounts, you must define some more detailed wallet file format (which could be built on top of this). On Wednesday, April 23, 2014 8:04:35 PM you wrote: > On 23.04.2014, at 22:02, Luke-Jr 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. > > > > No it doesn't... Just the assigned scriptPubKey and secret(s) required to > > satisfy it. > > 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. Sure, it *knows* what address was used to receive it. But at the point it's a UTXO, that address is no longer relevant. Luke