Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.46 as permitted sender)
	client-ip=209.85.192.46; envelope-from=etotheipi@gmail.com;
	helo=mail-qg0-f46.google.com; 
Message-ID: <5424CFF3.50404@gmail.com>
Date: Thu, 25 Sep 2014 22:31:15 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <53F38542.2000704@monetas.net>
	<CAAS2fgT7eUDUHqwtuMF9cj0LvzHdZXxyan+c2ep1dQ8dQGOrHw@mail.gmail.com>
In-Reply-To: <CAAS2fgT7eUDUHqwtuMF9cj0LvzHdZXxyan+c2ep1dQ8dQGOrHw@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------070004030409000605030709"
Subject: Re: [Bitcoin-development] BIP43 Purpose code for voting pool HD
	wallets
Precedence: list

This is a multi-part message in MIME format.
--------------070004030409000605030709
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'm in favor of BIP43.

Adding a "Purpose" node can be used as an identifier for what kind of
tree is in the wallet file we're reading.   I can envision a few
different, common tree structures.  Perhaps using a non-hardened
first-layer derivation (we have clients who want this).  Similarly, my
proposal for a "No-collision mode" for multisig BIP32 trees
<http://sourceforge.net/p/bitcoin/mailman/message/32860512/> is another
variant that might get some traction but not everyone will use it.=20
These things could be "supported" by simply changing the BIP43 "Purpose"
index and wallet software could be designed to recognize and react to
the Purpose node for any number of different tree structures, and ignore
any trees that it doesn't recognize (or maybe be able to view the
balance across all the leaves of the tree but not expand it)

We have clients with special use-cases (complex multi-layer trees) that
are unlikely to be recycled across users.  In such cases we might just
use a "random" Purpose that is recognized by their system, and know that
other software won't mess with it.  Though it would be better if that
field was encoded in the root seed, instead.

Nonetheless, putting that extra layer between the root and the
"important" tree nodes provides flexibility to BIP32 as a whole.
-Alan


On 09/25/2014 09:53 PM, Gregory Maxwell wrote:
> On Tue, Aug 19, 2014 at 10:11 AM, Justus Ranvier <justus@monetas.net> w=
rote:
>> Two draft information BIPs are attached.
> I've pinged some people privately but also pinging the list=E2=80=A6 no=

> commentary on this proposal?
>
> -----------------------------------------------------------------------=
-------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Report=
s
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=3D154622311&iu=3D/4140/os=
tg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--------------070004030409000605030709
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I'm in favor of BIP43. <br>
    <br>
    Adding a "Purpose" node can be used as an identifier for what kind
    of tree is in the wallet file we're reading.   I can envision a few
    different, common tree structures.  Perhaps using a non-hardened
    first-layer derivation (we have clients who want this).  Similarly,
    my proposal for a <a
      href="http://sourceforge.net/p/bitcoin/mailman/message/32860512/">"No-collision
      mode" for multisig BIP32 trees</a> is another variant that might
    get some traction but not everyone will use it.  These things could
    be "supported" by simply changing the BIP43 "Purpose" index and
    wallet software could be designed to recognize and react to the
    Purpose node for any number of different tree structures, and ignore
    any trees that it doesn't recognize (or maybe be able to view the
    balance across all the leaves of the tree but not expand it)<br>
    <br>
    We have clients with special use-cases (complex multi-layer trees)
    that are unlikely to be recycled across users.  In such cases we
    might just use a "random" Purpose that is recognized by their
    system, and know that other software won't mess with it.  Though it
    would be better if that field was encoded in the root seed, instead.<br>
    <br>
    Nonetheless, putting that extra layer between the root and the
    "important" tree nodes provides flexibility to BIP32 as a whole.<br>
    -Alan<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 09/25/2014 09:53 PM, Gregory Maxwell
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAS2fgT7eUDUHqwtuMF9cj0LvzHdZXxyan+c2ep1dQ8dQGOrHw@mail.gmail.com"
      type="cite">
      <pre wrap="">On Tue, Aug 19, 2014 at 10:11 AM, Justus Ranvier <a class="moz-txt-link-rfc2396E" href="mailto:justus@monetas.net">&lt;justus@monetas.net&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Two draft information BIPs are attached.
</pre>
      </blockquote>
      <pre wrap="">
I've pinged some people privately but also pinging the list… no
commentary on this proposal?

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a>
_______________________________________________
Bitcoin-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070004030409000605030709--