1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jan.moller@gmail.com>) id 1WcWQj-0004G7-JA
for bitcoin-development@lists.sourceforge.net;
Tue, 22 Apr 2014 08:51:53 +0000
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;
Received: from mail-qg0-f54.google.com ([209.85.192.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WcWQe-0001oS-9d
for bitcoin-development@lists.sourceforge.net;
Tue, 22 Apr 2014 08:51:53 +0000
Received: by mail-qg0-f54.google.com with SMTP id z60so4953905qgd.41
for <bitcoin-development@lists.sourceforge.net>;
Tue, 22 Apr 2014 01:51:42 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.224.119.141 with SMTP id z13mr46851557qaq.48.1398156702806;
Tue, 22 Apr 2014 01:51:42 -0700 (PDT)
Received: by 10.140.24.201 with HTTP; Tue, 22 Apr 2014 01:51:42 -0700 (PDT)
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
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(jan.moller[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.54 listed in list.dnswl.org]
X-Headers-End: 1WcWQe-0001oS-9d
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
Reply-To: jan.moller@gmail.com
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:51:53 -0000
--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'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"><<a href=3D"mailto:bip@ma=
ttwhitlock.name" target=3D"_blank">bip@mattwhitlock.name</a>></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>
> Necessary Shares =3D M+1, not a problem<br>
><br>
> I would probably encode N-of-M in 1 byte as I don't see good use c=
ases with<br>
> more than 17 shares. Anyway, I am fine with it as it is.<br>
<br>
</div>I agree that M > 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're conce=
rned about space, you can omit it (and the checksum).<br>
</blockquote></div><br></div>
--047d7bacbaaa9c932304f79db9a4--
|
