From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd3th-00087g-ED for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:36:01 +0000 X-ACL-Warn: Received: from mail-ee0-f50.google.com ([74.125.83.50]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd3tf-0000MU-NK for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:36:01 +0000 Received: by mail-ee0-f50.google.com with SMTP id c13so1146531eek.37 for ; Wed, 23 Apr 2014 13:35:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VmoSk2gIHTrk3+ko2MKrQoZoeHmOtgeCCqvYJw0Oa0k=; b=cxuXOB1pyMli1D0dWmVOaSLnnkpDjyXG0Iixdtrs8wSomgBjnKr1gFxYIUTQskvQi7 rviByU8vh5ocIVjqUSCQwLc4EPTSeQhNDJrryqRNJP+QKwE1iuvLGec3jdlIZN1iSXPB Rm9fuIWw4X9rewB0SuMUiU2ij8c6Gk2EThQkGeZxB07UaMAWI3w31adD+eftNhZ5Bk4e //sVeHxzttzG9Z7jdsAN1gKZjrPjPMg5cpp1SkpF9avNjGSwa0jMHhAN3fo8v5qsmEJo oGXzhXNnBvxAmLFPani3jImw9E1xHUfWj2/0Hn8c4po7Wn1TKacGsp/ZgIOdq7pwz2VZ 9y3A== X-Gm-Message-State: ALoCoQlr3gH5stzDV3m29kpMuxrPCMd7JpDtuRDtDnxJTrrfLCvPWgO5lIvouf0W+plZfGBuaXG+ X-Received: by 10.15.50.136 with SMTP id l8mr21101924eew.73.1398285353145; Wed, 23 Apr 2014 13:35:53 -0700 (PDT) Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254]) by mx.google.com with ESMTPSA id x45sm9369990eef.15.2014.04.23.13.35.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 13:35:52 -0700 (PDT) Message-ID: <53582426.4030601@gk2.sk> Date: Wed, 23 Apr 2014 22:35:50 +0200 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <201404232009.08791.luke@dashjr.org> <53581FAD.5010806@gk2.sk> <201404232032.08740.luke@dashjr.org> In-Reply-To: <201404232032.08740.luke@dashjr.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 1Wd3tf-0000MU-NK 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:36:01 -0000 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. > 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. -- Best Regards / S pozdravom, Pavol Rusnak