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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WVu1c-0006xH-Un
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 02:38:36 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.160.176 as permitted sender)
client-ip=209.85.160.176; envelope-from=jgarzik@bitpay.com;
helo=mail-yk0-f176.google.com;
Received: from mail-yk0-f176.google.com ([209.85.160.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WVu1b-0005gi-70
for bitcoin-development@lists.sourceforge.net;
Fri, 04 Apr 2014 02:38:36 +0000
Received: by mail-yk0-f176.google.com with SMTP id 19so2391717ykq.35
for <bitcoin-development@lists.sourceforge.net>;
Thu, 03 Apr 2014 19:38:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=jSedtQPX2MENYJN37JhoLktk2vdVgLYA1YgGtsrcf54=;
b=dGZ9jxuquP1Wwn0yEMz8gyqxk3OdgdmgkLD4wj31pWtfJv5KhCW5PthwhxQee1kV1k
pZoWSJx7eHmpGu/mReNocKd2kgaHf4U/jaLFsg7VKmUNnRMeKT5Dn1v9TjNd4jOXRZ7N
wtzWbDXMF8RyRG+ttxoTSPYtmuH2LfsUonTnYvISi6e2jSDQ2yPftbTc1FweJ/VpPQcU
q8HMX9iRS5cpfU7ws5qcddsY8wpShuv5a1IAseRS1Q32tALX587xDaE5Bg+Qv2O7y0q+
lbPFQ8Bdvm74IRFl/jck6vxXotz6ICeoZEROFc/R6An3hs0G0OiGLfMI1zhnIgHWL5DI
w6Jw==
X-Gm-Message-State: ALoCoQn4latlxF7aEgxFsAufbreo5m+wpxT5op4ypbO/9ZZqIUkJ7PXA4THxexiCcWpLTUJgqGIs
X-Received: by 10.236.63.103 with SMTP id z67mr13370220yhc.2.1396579109569;
Thu, 03 Apr 2014 19:38:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.162.214 with HTTP; Thu, 3 Apr 2014 19:38:09 -0700 (PDT)
In-Reply-To: <1701822.mCYDUGhe8d@crushinator>
References: <CACsn0ckScTWG4YxNCscxvtdsmcUkxtR2Gi-rdBs2HCkirPz5rA@mail.gmail.com>
<2135731.4HGHfZWzo5@crushinator> <53370C11.7040109@gmail.com>
<1701822.mCYDUGhe8d@crushinator>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 3 Apr 2014 22:38:09 -0400
Message-ID: <CAJHLa0Mvxa0BmTiZrB9PSkGNJ_XDrv3+eVu1NqyRKhKMGyr+OQ@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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
X-Headers-End: 1WVu1b-0005gi-70
Cc: Bitcoin Dev <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: Fri, 04 Apr 2014 02:38:37 -0000
On Sat, Mar 29, 2014 at 2:10 PM, Matt Whitlock <bip@mattwhitlock.name> wrote:
> Okay, you've convinced me. However, it looks like the consensus here is that my BIP is unneeded, so I'm not sure it would be worth the effort for me to improve it with your suggestions.
Discussion of whether you should or should not use SSS is separate
from whether you should or should not write a BIP.
If people are using SSS in the field, it is better to write a BIP than
not. Informational BIPs describing existing practice can be useful.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
