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 1Wd4Or-0005LE-E6 for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:08:13 +0000 X-ACL-Warn: Received: from mail-vc0-f178.google.com ([209.85.220.178]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd4Oq-00048Y-2j for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 21:08:13 +0000 Received: by mail-vc0-f178.google.com with SMTP id hu19so1865743vcb.37 for ; Wed, 23 Apr 2014 14:08:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=gJqEqbg15WVwreHNJMxHlhYXY92fy7q2JsUMmfbYNE4=; b=fb0ZifnCiTiS8tV8kRWPW1MWQkCUZs6L+u/Hoy+Xo0Bw9UAWN5bQj3xxbo7rRWaokX 9sarEaACM89nOxIJqRg6OOfi8hlRuwJXR8g01ZAxOyUE40/TEM4sSK/Rq1qSuQqsIepi MWgdJPHrWCinWDo3gFcZaZLFbTyCnmp+gC2YEPgtHpZyxHIT0g0r0DOYEomfMx8HsER9 g9/JAlW+2QZY4fKB38UVtlu+pXGPfDipfTw4Iy0KAoEkgrnzScgj4fNSnn7IbD8VbfX9 tS5G3yOxJ1r9zghsOqWIPmk9PN1cWSQdvBFrA5TVau4TsjeissoRTmna8nk8fcvZgL8K z+dQ== X-Gm-Message-State: ALoCoQl8wwkNNxZZqsQeiZCnV72jPq04Y7BrPBYFRPKD9prckNDuk/IdrplFaqHZ6Y96fbCMXr29 X-Received: by 10.52.173.165 with SMTP id bl5mr36892530vdc.13.1398287286515; Wed, 23 Apr 2014 14:08:06 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.234.68 with HTTP; Wed, 23 Apr 2014 14:07:36 -0700 (PDT) In-Reply-To: References: <201404232032.08740.luke@dashjr.org> <53582426.4030601@gk2.sk> <201404232041.14664.luke@dashjr.org> <5358260D.9040607@gk2.sk> From: slush Date: Wed, 23 Apr 2014 23:07:36 +0200 X-Google-Sender-Auth: lHRa8vTTsgzUEVp-mrb4paG-9ao Message-ID: To: Pieter Wuille Content-Type: multipart/alternative; boundary=bcaec51b9cfd01ce5b04f7bc21bd X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1Wd4Oq-00048Y-2j Cc: Bitcoin Dev 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 21:08:13 -0000 --bcaec51b9cfd01ce5b04f7bc21bd Content-Type: text/plain; charset=ISO-8859-1 On Wed, Apr 23, 2014 at 10:54 PM, Pieter Wuille wrote: > > 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? > > No, because one of requirement of BIP64 is to do not mix addressess between accounts. Without handling those accounts fully, it won't pass this requirement. ("This level [accounts] splits the key space into independent user identities, so the wallet never mixes the coins across different accounts.") Marek --bcaec51b9cfd01ce5b04f7bc21bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Apr 23, 2014 at 10:54 PM, Pieter Wuille <pieter.wuille@gmail.c= om> wrote:

Would you consider software which scans all accounts as specified by<= br> 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?


No, because one of requirement of BIP6= 4 is to do not mix addressess between accounts. Without handling those acco= unts fully, it won't pass this requirement.

("This level [account= s] splits the key space into independent user identities, so the wallet nev= er mixes the coins across different accounts.")
=A0

Marek

--bcaec51b9cfd01ce5b04f7bc21bd--