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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bip@mattwhitlock.name>) id 1WTxPZ-0003Pj-Kv
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 17:51:17 +0000
X-ACL-Warn:
Received: from qmta02.westchester.pa.mail.comcast.net ([76.96.62.24])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WTxPX-0007tb-VD for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 17:51:17 +0000
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28])
by qmta02.westchester.pa.mail.comcast.net with comcast
id jVoi1n0050cZkys51VrAc7; Sat, 29 Mar 2014 17:51:10 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
by omta10.westchester.pa.mail.comcast.net with comcast
id jVrA1n0084VnV2P3WVrATW; Sat, 29 Mar 2014 17:51:10 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: devrandom <c1.sf-bitcoin@niftybox.net>
Date: Sat, 29 Mar 2014 13:51:10 -0400
Message-ID: <3907269.Xk0HfD5vm0@crushinator>
User-Agent: KMail/4.12.3 (Linux/3.12.13-gentoo; KDE/4.12.3; x86_64; ; )
In-Reply-To: <1396115305.27001.8.camel@mimiz>
References: <CACsn0ckScTWG4YxNCscxvtdsmcUkxtR2Gi-rdBs2HCkirPz5rA@mail.gmail.com>
<3760502.BsfnhHlzm1@crushinator> <1396115305.27001.8.camel@mimiz>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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.24 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: 1WTxPX-0007tb-VD
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: Sat, 29 Mar 2014 17:51:17 -0000
On Saturday, 29 March 2014, at 10:48 am, devrandom wrote:
> On Sat, 2014-03-29 at 13:38 -0400, Matt Whitlock wrote:
> > Threshold ECDSA certainly sounds nice, but is anyone working on a BIP
> > for it? I would take it on myself, but I don't understand it well
> > enough yet, and publicly available information on it seems lacking. I
> > proposed this Shamir Secret Sharing BIP as an easily understood, easily
> > implemented measure that we can use today, with no changes to existing
> > Bitcoin software. It's low-hanging fruit.
>
> Good points, although multisig is catching on quickly in the ecosystem.
> AFAIK, all production wallets can send to p2sh addresses.
As far as I know, Blockchain.info wallets still can't send to P2SH addresses. This was a *major* roadblock in the Bitcoin project that I've been working on for the past several months, and it was the impetus for my creating this Shamir Secret Sharing implementation in the first place.
|
