Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.54 as permitted sender)
	client-ip=209.85.192.54; envelope-from=jan.moller@gmail.com;
	helo=mail-qg0-f54.google.com; 
MIME-Version: 1.0
In-Reply-To: <3412253.yhU6ROQD4n@crushinator>
References: <CAC7yFxSE8-TWPN-kuFiqdPKMDuprbiVJi7-z-ym+AUyA_f-xJw@mail.gmail.com>
	<2336265.urqHVhRi8n@crushinator>
	<CABh=4qPX=w4815O1bRSu+y-KviKS=Brai-umgmheZM5Ar6xv1w@mail.gmail.com>
	<3412253.yhU6ROQD4n@crushinator>
Date: Tue, 22 Apr 2014 10:51:42 +0200
Message-ID: <CABh=4qOovPggRYo410TTZ7oT2vDfF8RMqPwK8WDr=tPZrw9zdA@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=047d7bacbaaa9c932304f79db9a4
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

--047d7bacbaaa9c932304f79db9a4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am concerned about space, but more about usability :-)
 I'll definitely use both M and the checksum.


On Tue, Apr 22, 2014 at 10:43 AM, Matt Whitlock <bip@mattwhitlock.name>wrot=
e:

> On Tuesday, 22 April 2014, at 10:39 am, Jan M=C3=B8ller wrote:
> > Necessary Shares =3D M+1, not a problem
> >
> > I would probably encode N-of-M in 1 byte as I don't see good use cases
> with
> > more than 17 shares. Anyway, I am fine with it as it is.
>
> I agree that M > 16 is probably not a viable use case for human beings,
> but machines would probably be able to make use of it. I, for one, welcom=
e
> our new robot overlords.
>
> Also, the byte that encodes M=E2=88=921 is optional, so if you're concern=
ed about
> space, you can omit it (and the checksum).
>

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

<div dir=3D"ltr">I am concerned about space, but more about usability :-)<d=
iv>=C2=A0I&#39;ll definitely use both M and the checksum.</div></div><div c=
lass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr 22, 201=
4 at 10:43 AM, Matt Whitlock <span dir=3D"ltr">&lt;<a href=3D"mailto:bip@ma=
ttwhitlock.name" target=3D"_blank">bip@mattwhitlock.name</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Tuesday, 22 April 2014, a=
t 10:39 am, Jan M=C3=B8ller wrote:<br>
&gt; Necessary Shares =3D M+1, not a problem<br>
&gt;<br>
&gt; I would probably encode N-of-M in 1 byte as I don&#39;t see good use c=
ases with<br>
&gt; more than 17 shares. Anyway, I am fine with it as it is.<br>
<br>
</div>I agree that M &gt; 16 is probably not a viable use case for human be=
ings, but machines would probably be able to make use of it. I, for one, we=
lcome our new robot overlords.<br>
<br>
Also, the byte that encodes M=E2=88=921 is optional, so if you&#39;re conce=
rned about space, you can omit it (and the checksum).<br>
</blockquote></div><br></div>

--047d7bacbaaa9c932304f79db9a4--