Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTx47-0004K8-Jr for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 17:29:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of niftybox.net designates 95.142.167.147 as permitted sender) client-ip=95.142.167.147; envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to; Received: from i3.hyper.to ([95.142.167.147]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WTx46-00072d-7w for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 17:29:07 +0000 Received: from localhost (localhost [127.0.0.1]) by i3.hyper.to (Postfix) with ESMTP id 1235DE0531; Sat, 29 Mar 2014 18:29:00 +0100 (CET) Received: from i3.hyper.to ([127.0.0.1]) by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0RBzeCla3MBn; Sat, 29 Mar 2014 18:28:59 +0100 (CET) Received: from [192.168.4.81] (50-1-105-185.dsl.dynamic.sonic.net [50.1.105.185]) by i3.hyper.to (Postfix) with ESMTPSA id 9D95DE0513; Sat, 29 Mar 2014 18:28:58 +0100 (CET) Message-ID: <1396114136.27001.1.camel@mimiz> From: devrandom To: Matt Whitlock Date: Sat, 29 Mar 2014 10:28:56 -0700 In-Reply-To: <4906130.DUyjhm1C93@crushinator> References: <4906130.DUyjhm1C93@crushinator> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WTx46-00072d-7w Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret Sharing of Bitcoin private keys 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: Sat, 29 Mar 2014 17:29:07 -0000 On Sat, 2014-03-29 at 11:44 -0400, Matt Whitlock wrote: > On Saturday, 29 March 2014, at 11:08 am, Watson Ladd wrote: > > https://freedom-to-tinker.com/blog/stevenag/new-research-better-wallet-security-for-bitcoin/ > > Thanks. This is great, although it makes some critical references to an > ACM paper for which no URL is provided, and thus I cannot implement it. > > A distributed ECDSA notwithstanding, we still need a way to decompose a > BIP32 master seed into shares. I am envisioning a scenario in which I It would seem that threshold ECDSA with keys derived from separate seeds has better security properties than one seed that is then split up. The main thing is that there is no single point of attack in the generation or signing. > might meet my sudden and untimely demise, and I wish to allow my > beneficiaries to reconstruct my wallet's master seed after my death. I > would like to distribute seed shares to each of my beneficiaries and > some close friends, such that some subset of the shares must be joined > together to reconstitute my master seed. Shamir's Secret Sharing Scheme > is perfect for this use case. I am presently working on extending my > draft BIP so that it also applies to BIP32 master seeds of various > sizes. > > ------------------------------------------------------------------------------ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- -- Miron / devrandom -- -- Miron / devrandom