Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd3yt-0004Di-0w for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:41:23 +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 1Wd3yr-00034v-Ta for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:41:22 +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 EE9E1108011E; Wed, 23 Apr 2014 20:41:51 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Wed, 23 Apr 2014 20:41:13 +0000 User-Agent: KMail/1.13.7 (Linux/3.12.6-gentoo; KDE/4.11.5; x86_64; ; ) References: <201404232032.08740.luke@dashjr.org> <53582426.4030601@gk2.sk> In-Reply-To: <53582426.4030601@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: <201404232041.14664.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: 1Wd3yr-00034v-Ta 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:41:23 -0000 On Wednesday, April 23, 2014 8:35:50 PM Pavol Rusnak wrote: > On 04/23/2014 10:32 PM, Luke-Jr wrote: > > f) I missed the part where BIP 32 redefined "account" to mean "subwallet" > > instead of what has traditionally been called "account" in Bitcoin. > > Ah, okay. The last time I saw Bitcoin-qt it was still using independent > addresses. It is. Accounts have been a bitcoind feature since before 0.4. > > In that case, single-subwallet wallet software probably needs to have the > > user provide a subwallet number in addition to the seed. > > Which brings us back to my original complaint that the user can be > confused because he doesn't see all his funds. I don't see how. The user knows he has money in different subwallets. As long as he has a way to specify which subwallet he is accessing in single-subwallet clients, there shouldn't be a problem. Luke