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"
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

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).