Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1F795258 for ; Wed, 25 Apr 2018 09:35:09 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0104.outbound.protection.outlook.com [104.47.1.104]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4266D687 for ; Wed, 25 Apr 2018 09:35:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=345systems.onmicrosoft.com; s=selector1-345-systems; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MhY0BuDlBbKsWMM0d/AYr95VQrhaz4pFbhvCromacb0=; b=lKUzew2bkFIoHkOAtcjWCDRbj8zcQcW4NoL3m332p/INEbmj76LxYuqWq41Hw75BFFGWaR0fUlZSuU6WTM6wjGkCZIp6xKKzojo9jb6Qw8zkLNWTlb/8bG0AStXpFYOTsfAYQ8nu2WzmBpy6m9luGwUbeCiUEmKyjAudiaaOfdQ= Received: from HE1PR09MB0266.eurprd09.prod.outlook.com (10.161.117.20) by HE1PR09MB0764.eurprd09.prod.outlook.com (10.169.123.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.696.13; Wed, 25 Apr 2018 09:35:03 +0000 Received: from HE1PR09MB0266.eurprd09.prod.outlook.com ([fe80::68eb:90ce:2170:5824]) by HE1PR09MB0266.eurprd09.prod.outlook.com ([fe80::68eb:90ce:2170:5824%13]) with mapi id 15.20.0696.020; Wed, 25 Apr 2018 09:35:03 +0000 From: Paul Brown To: "bitcoin-dev@lists.linuxfoundation.org" Thread-Topic: Multi-signature and multi-coin HD wallet in one BIP32 derivation path (new BIP) Thread-Index: AdPcd2nXXfizUfmCR2G/JOw0hbrwCg== Date: Wed, 25 Apr 2018 09:35:03 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=paul@345.systems; x-originating-ip: [5.80.175.8] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; HE1PR09MB0764; 7:quRcsjwITLsE7wJJBdvyXmw8Vn52oGDYeT32PzEWvtKepbEyCmwhlgSi9luI+RDveLE0P+sljs0dekMTvi8PwOpHPRsX+bVtSxoT7OcbARd3JdK1lotYV42JmQ7Xyqqx3cCLd5gR4eQcIRn4nNcoDB101VEjCduHy1yhyRXck+Da4BdwR/iS6cmUiJ+StTMwSnjcUfvs6/gNNetnAlj6xH/FqlQ7ylwfjBMb7+H1SNi2k1iWLIVJaHYo6h0Ps/8w x-ms-exchange-antispam-srfa-diagnostics: SOS; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:HE1PR09MB0764; x-ms-traffictypediagnostic: HE1PR09MB0764: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(143289334528602)(28532068793085)(166708455590820)(42262312472803)(21748063052155)(278021516957215); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3231232)(944501410)(52105095)(3002001)(6041310)(20161123560045)(20161123562045)(20161123558120)(2016111802025)(20161123564045)(6043046)(6072148)(201708071742011); SRVR:HE1PR09MB0764; BCL:0; PCL:0; RULEID:; SRVR:HE1PR09MB0764; x-forefront-prvs: 06530126A4 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(366004)(376002)(396003)(346002)(39830400003)(199004)(189003)(236005)(5660300001)(9686003)(53936002)(2351001)(97736004)(26005)(66066001)(99286004)(55016002)(6306002)(316002)(54896002)(5640700003)(106356001)(105586002)(606006)(8676002)(81156014)(8936002)(7696005)(81166006)(33656002)(7736002)(5250100002)(102836004)(71446004)(2501003)(6916009)(3846002)(6116002)(790700001)(59450400001)(6506007)(14454004)(9326002)(6436002)(478600001)(186003)(74316002)(486006)(2900100001)(68736007)(966005)(21615005)(3280700002)(3660700001)(86362001)(25786009)(476003)(2906002)(46492003); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR09MB0764; H:HE1PR09MB0266.eurprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: 345.systems does not designate permitted sender hosts) x-microsoft-antispam-message-info: QLAV/ytTPUTsELbivDGAcOt18ylzZ58nWaT2uioPa+DjGpahg8x2sk76RwDBvhOjOEhBJkAcF1mdqFgZ+53EtNMDlS4mgLtHAXygzJkuBrjS0XQFWKT5zvZs7HmF3jA7r36i9POd/lNjPr42eH4p1oeZPZLYgPQK/9A2jUM+KoGgnI66fw4aNHpEualx4EZ9 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_HE1PR09MB026619CDFFBA6D995600EF18988F0HE1PR09MB0266eurp_" MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: d3a03095-6dda-44fd-3574-08d5aa8fd2e8 X-OriginatorOrg: 345.systems X-MS-Exchange-CrossTenant-Network-Message-Id: d3a03095-6dda-44fd-3574-08d5aa8fd2e8 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2018 09:35:03.7803 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ca2d4186-9a44-49c0-a437-c7c7bbca555e X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR09MB0764 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 25 Apr 2018 12:36:05 +0000 Subject: [bitcoin-dev] Multi-signature and multi-coin HD wallet in one BIP32 derivation path (new BIP) 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: Wed, 25 Apr 2018 09:35:09 -0000 --_000_HE1PR09MB026619CDFFBA6D995600EF18988F0HE1PR09MB0266eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi I have written a new BIP describing a BIP32 derivation path that supports a= single or multi-signature and multi-coin wallet from a single master seed.= It combines BIP44 and BIP45 and adds in a self-describing structure in th= e derivation path for multiple multi-sig combinations within the single wal= let along with an extended public key export file format for public key dis= tribution between parties. I can particularly see this being useful for mu= ltiple Lightning Network 2of2 accounts for different payment channels. The BIP can be found here: https://github.com/gluexchange/bip/blob/master/b= ip-0046.mediawiki I appreciate that this might be re-hashing old ground as BIP44 in particula= r has been widely adopted, however, BIP44 does leave itself open to a lot o= f interpretation from a wallet portability perspective such as: - What address format is expected when discovering balances and creating tr= ansactions? - Does the master seed represent a single-sig or multi-sig wallet? - If multi-sig, how many cosigners and what are their extended public keys = (so that the wallet can generate the correctly formatted redeem script with= public keys in the right order)? - If multi-sig, how do you prevent collisions on the same address index (in= a wallet that is occasionally connected)? BIP45 solves the collision that occurs when the individual parties in a mul= ti-sig group each give out a new address from a wallet, where the wallet ha= sn't been able to sync to mark the address as 'used' (this could happen if = they gave out addresses independently at the same time). It uses a cosigne= r index in the derivation path so that each party has their own path to the= ir addresses. However, BIP45 drops the multi-coin support that BIP44 has. This is a useful discussion on the problems of a collision and the merits o= f separating cosigners in the derivation path: https://www.mail-archive.com= /bitcoin-development@lists.sourceforge.net/msg05188.html For the purposes of the BIP text (and the example paths used to generate ke= ys) I've temporarily assigned it the number 46. It looks like that is avai= lable and seemed somewhat appropriate given that it builds on the good work= of BIP44 and BIP45. Paul Brown --_000_HE1PR09MB026619CDFFBA6D995600EF18988F0HE1PR09MB0266eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi

 

I have written a new BIP describing a BIP32 derivati= on path that supports a single or multi-signature and multi-coin wallet fro= m a single master seed.  It combines BIP44 and BIP45 and adds in a sel= f-describing structure in the derivation path for multiple multi-sig combinations within the single wallet along wi= th an extended public key export file format for public key distribution be= tween parties.  I can particularly see this being useful for multiple = Lightning Network 2of2 accounts for different payment channels.

 

The BIP can be found here: https://github.com/gluexchange/bip/blob/master/bip-0046.mediawiki<= /o:p>

 

I appreciate that this might be re-hashing old groun= d as BIP44 in particular has been widely adopted, however, BIP44 does leave= itself open to a lot of interpretation from a wallet portability perspecti= ve such as:

 

- What address format is expected when discovering b= alances and creating transactions?

- Does the master seed represent a single-sig or mul= ti-sig wallet?

- If multi-sig, how many cosigners and what are thei= r extended public keys (so that the wallet can generate the correctly forma= tted redeem script with public keys in the right order)?

- If multi-sig, how do you prevent collisions on the= same address index (in a wallet that is occasionally connected)?

 

BIP45 solves the collision that occurs when the indi= vidual parties in a multi-sig group each give out a new address from a wall= et, where the wallet hasn’t been able to sync to mark the address as = ‘used’ (this could happen if they gave out addresses independently at the same time).  It uses a cosigner index = in the derivation path so that each party has their own path to their addre= sses.  However, BIP45 drops the multi-coin support that BIP44 has.

 

This is a useful discussion on the problems of a col= lision and the merits of separating cosigners in the derivation path: https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg0= 5188.html

 

For the purposes of the BIP text (and the example pa= ths used to generate keys) I’ve temporarily assigned it the number 46= .  It looks like that is available and seemed somewhat appropriate giv= en that it builds on the good work of BIP44 and BIP45.

 

Paul Brown

 

 

--_000_HE1PR09MB026619CDFFBA6D995600EF18988F0HE1PR09MB0266eurp_--