From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 62A8EC09 for ; Fri, 14 Apr 2017 19:26:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx-out02.mykolab.com (mx.kolabnow.com [95.128.36.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7AAC9108 for ; Fri, 14 Apr 2017 19:26:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) by mx-out02.mykolab.com (Postfix) with ESMTPS id C135B607C6 for ; Fri, 14 Apr 2017 21:26:13 +0200 (CEST) From: Tom Zander To: bitcoin-dev@lists.linuxfoundation.org Date: Fri, 14 Apr 2017 21:26:14 +0200 Message-ID: <2112201.An0daUyfG4@cherry> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Fri, 14 Apr 2017 19:41:29 +0000 Subject: Re: [bitcoin-dev] BIP proposal draft: BIP43 "purpose" allocation for Ethereum X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 19:26:17 -0000 Thinking about this a bit, I support this proposal for a BIP. This is not Bitcoin, but address types are bound to meet in meat-space and it would be good to have a central place where this is defined. I would very much appreciate someone that worked on BIP32/BIP43 itself to comment on the details. Quoting bip 43; "We encourage different schemes to apply for assigning a separate BIP number and use the same number for purpose field, so addresses won't be generated from overlapping BIP32 spaces." On Wednesday, 12 April 2017 12:02:37 CEST Nick Johnson via bitcoin-dev wrote: > 
>   BIP: bip-nickjohnson-ethereum-purpose
>   Layer: Applications
>   Title: Ethereum purpose allocation for Deterministic Wallets
>   Author: Nick Johnson 
>   Status: Proposed
>   Type: Standards Track
>   Created: 2017-04-12
>
> > ==Abstract== > > This BIP defines a logical hierarchy for deterministic wallets on the > Ethereum blockchain based on an algorithm described in BIP-0032 (BIP32 > from now on) and purpose scheme described in BIP-0043 (BIP43 from now > on). > > This BIP is a particular application of BIP43. > > ==Motivation== > > Because Ethereum is based on account balances rather than UTXO, the > hierarchy defined by BIP44 is poorly suited. As a result, several > competing derivation path strategies have sprung up for deterministic > wallets, resulting in inter-client incompatibility. This BIP seeks to > provide a path to standardise this in a fashion better suited to > Ethereum's unique requirements. > > ==Path levels== > > We define the following 2 levels in BIP32 path: > > 
> m / purpose' / subpurpose' / *
>
> > Apostrophe in the path indicates that BIP32 hardened derivation is used. > > Each level has a special meaning, described in the chapters below. > > ===Purpose=== > > Purpose is a constant set to the hardened value of the BIP number assigned > to this BIP (equivalently, the BIP number, bitwise ORed with 0x80000000) > following the BIP43 recommendation. > It indicates that the subtree of this node is used according to this > specification. > > Hardened derivation is used at this level. > > ===Subpurpose=== > Subpurpose is set to the EIP number specifying the remainder of the BIP32 > derivation path. This permits new Ethereum-focused applications of > deterministic wallets without needing to interface with the BIP process. > > Hardened derivation is used at this level. > > ==Reference== * [[bip-0032.mediawiki|BIP32 - Hierarchical Deterministic > Wallets]] * [[bip-0043.mediawiki|BIP43 - Purpose Field for Deterministic > Wallets]] -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel