From: Mike Hearn <mike@plan99•net>
To: Chris Pacia <ctpacia@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Update on mobile 2-factor wallets
Date: Sat, 8 Nov 2014 20:36:07 +0100 [thread overview]
Message-ID: <CANEZrP3EWXDwXefzeFfEYS=KBVPLnu-dNxufAZQnednmhFPBWw@mail.gmail.com> (raw)
In-Reply-To: <CAB+qUq6CxOZpdS+E7rpBmY=4VBiOr845096TUv7koaNXD8gAMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
>
> I am familiar with the Princeton threshold signature but I was under the
> impression a single key needed to be generated on a single device then
> split and distributed.
>
> Does this scheme work the same way?
>
No, it doesn't. Neither device ever sees as master private key.
[-- Attachment #2: Type: text/html, Size: 515 bytes --]
prev parent reply other threads:[~2014-11-08 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 16:04 Mike Hearn
2014-11-08 16:21 ` Jeff Garzik
2014-11-08 16:37 ` Mike Hearn
2014-11-08 18:43 ` Chris Pacia
2014-11-08 19:36 ` Mike Hearn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP3EWXDwXefzeFfEYS=KBVPLnu-dNxufAZQnednmhFPBWw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=ctpacia@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox