diff options
| author | Gregory Maxwell <gmaxwell@gmail.com> | 2014-03-29 07:36:58 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-03-29 14:37:05 +0000 |
| commit | 3c9ca8fca5b32821b292871e58aeb812f6382892 (patch) | |
| tree | 6d8a39b5037a8e27fad0e0202cf86e66bc76b063 | |
| parent | ccb2bd37276ab2e858ec16ba17d426b9c6696e8c (diff) | |
| download | pi-bitcoindev-3c9ca8fca5b32821b292871e58aeb812f6382892.tar.gz pi-bitcoindev-3c9ca8fca5b32821b292871e58aeb812f6382892.zip | |
Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret Sharing of Bitcoin private keys
| -rw-r--r-- | db/af4a78750e5f9c6a00e195b6b162497e75679f | 86 |
1 files changed, 86 insertions, 0 deletions
diff --git a/db/af4a78750e5f9c6a00e195b6b162497e75679f b/db/af4a78750e5f9c6a00e195b6b162497e75679f new file mode 100644 index 000000000..f0299d724 --- /dev/null +++ b/db/af4a78750e5f9c6a00e195b6b162497e75679f @@ -0,0 +1,86 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gmaxwell@gmail.com>) id 1WTuNd-00073Q-Sm + for bitcoin-development@lists.sourceforge.net; + Sat, 29 Mar 2014 14:37:05 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.215.48 as permitted sender) + client-ip=209.85.215.48; envelope-from=gmaxwell@gmail.com; + helo=mail-la0-f48.google.com; +Received: from mail-la0-f48.google.com ([209.85.215.48]) + by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WTuNd-00018H-0P + for bitcoin-development@lists.sourceforge.net; + Sat, 29 Mar 2014 14:37:05 +0000 +Received: by mail-la0-f48.google.com with SMTP id gf5so4508848lab.21 + for <bitcoin-development@lists.sourceforge.net>; + Sat, 29 Mar 2014 07:36:58 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.112.85.6 with SMTP id d6mr9827727lbz.8.1396103818374; Sat, + 29 Mar 2014 07:36:58 -0700 (PDT) +Received: by 10.112.89.68 with HTTP; Sat, 29 Mar 2014 07:36:58 -0700 (PDT) +In-Reply-To: <CACsn0cn8cFn79dMi7M3uALE5KDFJOzxK4PdFyRR8j56FygnQZg@mail.gmail.com> +References: <1878927.J1e3zZmtIP@crushinator> + <CAJHLa0N0YCHfBeDq+QLqK3ZVWD-rAx85MXvX4OBqSoQqgCXm2w@mail.gmail.com> + <CANEZrP0WAMGV_ki3+9eFPaLQQVS7BJQ1c1c7KDuQatTeun-VwA@mail.gmail.com> + <1894130.91FUH3Vu6n@crushinator> + <CACsn0cn8cFn79dMi7M3uALE5KDFJOzxK4PdFyRR8j56FygnQZg@mail.gmail.com> +Date: Sat, 29 Mar 2014 07:36:58 -0700 +Message-ID: <CAAS2fgRCuQ+WtaMOr45cPh6bFmajweSAfPJse85Rh3bYjtdE3Q@mail.gmail.com> +From: Gregory Maxwell <gmaxwell@gmail.com> +To: Watson Ladd <wbl@uchicago.edu> +Content-Type: text/plain; charset=UTF-8 +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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (gmaxwell[at]gmail.com) + -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: 1WTuNd-00018H-0P +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 14:37:06 -0000 + +On Sat, Mar 29, 2014 at 7:28 AM, Watson Ladd <wbl@uchicago.edu> wrote: +> This is not the case: one can use MPC techniques to compute a +> signature from shares without reconstructing the private key. There is +> a paper on this for bitcoin, but I don't know where it is. + +Practically speaking you cannot unless the technique used is one +carefully selected to make it possible. This proposal isn't such a +scheme I beleieve, however, and I think I'd strongly prefer that we +BIP standardize a formulation which also has this property. + +The paper you want is +http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.67.9913 + +There will soon be a paper coming out from some princeton folks about +refining that and applying it to Bitcoin. + +You can use the secret sharing from threshold ecdsa in the +not-super-useful way where you just recombine the private key and +sign... but you can also use it to compute a secret shared signature +and then interpolate back the signature... avoiding the need for any +trusted device in holding the signature. + + |