Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.48 as permitted sender)
	client-ip=209.85.192.48; envelope-from=jan.moller@gmail.com;
	helo=mail-qg0-f48.google.com; 
MIME-Version: 1.0
In-Reply-To: <1927948.OEZHQcsQ9n@crushinator>
References: <CAC7yFxSE8-TWPN-kuFiqdPKMDuprbiVJi7-z-ym+AUyA_f-xJw@mail.gmail.com>
	<CAC7yFxR7XWtFSMeHgbMZOMKbr+kK_7Ezb7zBUQP08rfC0am9sQ@mail.gmail.com>
	<CABh=4qNaJht-MnnjEguZ=UOuXN3uQ-s4-dkDUVErbHj6W44J_g@mail.gmail.com>
	<1927948.OEZHQcsQ9n@crushinator>
Date: Tue, 22 Apr 2014 10:27:18 +0200
Message-ID: <CABh=4qOQhxEte3yQfCMNOZdedExtpqARQRDSfxQMqk-2KwJamw@mail.gmail.com>
From: =?UTF-8?Q?Jan_M=C3=B8ller?= <jan.moller@gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=001a1133c93854642604f79d62b3
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret
 Sharing of Bitcoin private keys
Precedence: list
Reply-To: jan.moller@gmail.com

--001a1133c93854642604f79d62b3
Content-Type: text/plain; charset=UTF-8

>
>
> >  - Please allow M=1. From a usability point of view it makes sense to
> allow
> > the user to select 1 share if that is what he wants.
>
> How does that make sense? Decomposing a key/seed into 1 share is
> functionally equivalent to dispensing with the secret sharing scheme
> entirely.
>
>
I agree that it may look silly to have just one-of-one share from a
technical point of view, but from an end-user point of view there could be
reasons for just having one piece of paper to manage. If M can be 1 then
the software/hardware doesn't have to support multiple formats,
import/export paths + UI  (one for SIPA keys in one share, one for HD seeds
in one share, one for SIPA keys + HD seeds in multiple shares).

Less complexity & more freedom of choice.

--001a1133c93854642604f79d62b3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D""><br>
&gt; =C2=A0- Please allow M=3D1. From a usability point of view it makes se=
nse to allow<br>
&gt; the user to select 1 share if that is what he wants.<br>
<br>
</div>How does that make sense? Decomposing a key/seed into 1 share is func=
tionally equivalent to dispensing with the secret sharing scheme entirely.<=
br>
<div class=3D""><br></div></blockquote><div><br></div><div>I agree that it =
may look silly to have just one-of-one share from a technical point of view=
, but from an end-user point of view there could be reasons for just having=
 one piece of paper to manage. If M can be 1 then the software/hardware doe=
sn&#39;t have to support multiple formats, import/export paths + UI =C2=A0(=
one for SIPA keys in one share, one for HD seeds in one share, one for SIPA=
 keys + HD seeds in multiple shares).</div>
<div><br></div><div>Less complexity &amp; more freedom of choice.</div><div=
><br></div></div></div></div>

--001a1133c93854642604f79d62b3--