From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <bip@mattwhitlock.name>) id 1WcWLn-000421-4F
	for bitcoin-development@lists.sourceforge.net;
	Tue, 22 Apr 2014 08:46:47 +0000
X-ACL-Warn: 
Received: from qmta05.westchester.pa.mail.comcast.net ([76.96.62.48])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1WcWLH-0005kk-Bz for bitcoin-development@lists.sourceforge.net;
	Tue, 22 Apr 2014 08:46:46 +0000
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35])
	by qmta05.westchester.pa.mail.comcast.net with comcast
	id swjm1n0010ldTLk55wjmps; Tue, 22 Apr 2014 08:43:46 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
	by omta04.westchester.pa.mail.comcast.net with comcast
	id swjl1n00F4VnV2P01wjmyk; Tue, 22 Apr 2014 08:43:46 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: jan.moller@gmail.com
Date: Tue, 22 Apr 2014 04:43:45 -0400
Message-ID: <3412253.yhU6ROQD4n@crushinator>
User-Agent: KMail/4.13 (Linux/3.12.13-gentoo; KDE/4.13.0; x86_64; ; )
In-Reply-To: <CABh=4qPX=w4815O1bRSu+y-KviKS=Brai-umgmheZM5Ar6xv1w@mail.gmail.com>
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>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [76.96.62.48 listed in list.dnswl.org]
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WcWLH-0005kk-Bz
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 08:46:47 -0000

On Tuesday, 22 April 2014, at 10:39 am, Jan M=C3=B8ller wrote:
> Necessary Shares =3D M+1, not a problem
>=20
> I would probably encode N-of-M in 1 byte as I don't see good use case=
s 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, wel=
come our new robot overlords.

Also, the byte that encodes M=E2=88=921 is optional, so if you're conce=
rned about space, you can omit it (and the checksum).