<oembed><type>rich</type><version>1.0</version><author_name>npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_name><author_url>https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-23&#xA;📝 Original message:On Wednesday, April 23, 2014 8:35:50 PM Pavol Rusnak wrote:&#xA;&gt; On 04/23/2014 10:32 PM, Luke-Jr wrote:&#xA;&gt; &gt; f) I missed the part where BIP 32 redefined &#34;account&#34; to mean &#34;subwallet&#34;&#xA;&gt; &gt; instead of what has traditionally been called &#34;account&#34; in Bitcoin.&#xA;&gt; &#xA;&gt; Ah, okay. The last time I saw Bitcoin-qt it was still using independent&#xA;&gt; addresses.&#xA;&#xA;It is. Accounts have been a bitcoind feature since before 0.4.&#xA;&#xA;&gt; &gt; In that case, single-subwallet wallet software probably needs to have the&#xA;&gt; &gt; user provide a subwallet number in addition to the seed.&#xA;&gt; &#xA;&gt; Which brings us back to my original complaint that the user can be&#xA;&gt; confused because he doesn&#39;t see all his funds.&#xA;&#xA;I don&#39;t see how. The user knows he has money in different subwallets. As long &#xA;as he has a way to specify which subwallet he is accessing in single-subwallet &#xA;clients, there shouldn&#39;t be a problem.&#xA;&#xA;Luke</html></oembed>