From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd3X9-0007CJ-Eh for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:12:43 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.178 as permitted sender) client-ip=209.85.223.178; envelope-from=pieter.wuille@gmail.com; helo=mail-ie0-f178.google.com; Received: from mail-ie0-f178.google.com ([209.85.223.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd3X8-0004Lj-Im for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:12:43 +0000 Received: by mail-ie0-f178.google.com with SMTP id lx4so1405028iec.23 for ; Wed, 23 Apr 2014 13:12:37 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.131.197 with SMTP id a5mr45350133ict.8.1398283957287; Wed, 23 Apr 2014 13:12:37 -0700 (PDT) Received: by 10.50.127.243 with HTTP; Wed, 23 Apr 2014 13:12:37 -0700 (PDT) Received: by 10.50.127.243 with HTTP; Wed, 23 Apr 2014 13:12:37 -0700 (PDT) In-Reply-To: <53581CB3.2000109@gk2.sk> References: <201404231955.09287.luke@dashjr.org> <201404232001.06679.luke@dashjr.org> <53581CB3.2000109@gk2.sk> Date: Wed, 23 Apr 2014 22:12:37 +0200 Message-ID: From: Pieter Wuille To: Pavol Rusnak Content-Type: multipart/alternative; boundary=bcaec53969d891c18504f7bb5a39 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wd3X8-0004Lj-Im 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 20:12:43 -0000 --bcaec53969d891c18504f7bb5a39 Content-Type: text/plain; charset=ISO-8859-1 I believe Luke means scanning chains as defined by the structure, but not handing out addresses from other accounts than the first one. That's certainly a possibly way to compatibly implement BIP64, but it doesn't reduce all that much complexity. I hope people would choose that over defining their own accountless structure though. On 23 Apr 2014 22:06, "Pavol Rusnak" wrote: > On 04/23/2014 10:01 PM, Luke-Jr wrote: > > Yes, it should scan all possible (under the BIP-defined structure) > branches > > regardless of which features it supports. > > So you suggest to scan for accounts, show balances but don't allow user > to spend them? Does not seem right to me. > > -- > Best Regards / S pozdravom, > > Pavol Rusnak > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --bcaec53969d891c18504f7bb5a39 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I believe Luke means scanning chains as defined by the struc= ture, but not handing out addresses from other accounts than the first one.=

That's certainly a possibly way to compatibly implement = BIP64, but it doesn't reduce all that much complexity. I hope people wo= uld choose that over defining their own accountless structure though.

On 23 Apr 2014 22:06, "Pavol Rusnak" &= lt;stick@gk2.sk> wrote:
On 04/23/2014 10:01 PM, Luke-Jr wrote:
> Yes, it should scan all possible (under the BIP-defined structure) bra= nches
> regardless of which features it supports.

So you suggest to scan for accounts, show balances but don't allow user=
to spend them? Does not seem right to me.

--
Best Regards / S pozdravom,

Pavol Rusnak <stick@gk2.sk>

---------------------------------------------------------------------------= ---
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.n= et/sfu/ExoPlatform
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment
--bcaec53969d891c18504f7bb5a39--