Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.169 as permitted sender)
	client-ip=209.85.213.169; envelope-from=pieter.wuille@gmail.com;
	helo=mail-ig0-f169.google.com; 
MIME-Version: 1.0
In-Reply-To: <5358260D.9040607@gk2.sk>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
	<201404232032.08740.luke@dashjr.org> <53582426.4030601@gk2.sk>
	<201404232041.14664.luke@dashjr.org> <5358260D.9040607@gk2.sk>
Date: Wed, 23 Apr 2014 22:54:48 +0200
Message-ID: <CAPg+sBjk4M6+9R=McwWcWda0Pw4u9oGiBR5NDAwpq3dntG6vtg@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Pavol Rusnak <stick@gk2.sk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list

On Wed, Apr 23, 2014 at 10:43 PM, Pavol Rusnak <stick@gk2.sk> wrote:
> On 04/23/2014 10:41 PM, Luke-Jr wrote:
>> 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.
>
> Right. But these clients have no right to call themselves BIP64
> compatible then.

Would you consider software which scans all accounts as specified by
BIP64, but has no user interface option to distinguish them in any
way, view them independently, and has no ability to keep the coins
apart... compatible with BIP64?

According to the argument here mentioned earlier ("all or nothing"),
it is, as it will not break interoperability with other BIP64
software. Still, it doesn't support the accounts feature, and perhaps
that's fine?

-- 
Pieter