From: "David A. Harding" <dave@dtrt•org>
To: Tim Ruffing <crypto@timruffing•de>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] BIP Draft: "ChillDKG: Distributed Key Generation for FROST"
Date: Tue, 16 Jul 2024 06:43:50 -1000 [thread overview]
Message-ID: <5ce152c9181ea552b8e146c9329f011b@dtrt.org> (raw)
In-Reply-To: <8768422323203aa3a8b280940abd776526fab12e.camel@timruffing.de>
On 2024-07-08 10:05, Tim Ruffing wrote:
> Jonas Nick and I have been working on a BIP draft for Distributed Key
> Generation for FROST Threshold Signatures
Thank you Tim and Jonas! This looks amazing! One quick question; you
write:
> Simple backups: The capability of ChillDKG to recover devices from a
> static seed and public recovery data avoids the need for secret
> per-session backups, enhancing user experience.
By "public recovery data", I assume you mean that security is not
weakened by the data being made public. However, are there any privacy
implications? For comparison, if everyone knows what BIP32 HD path I
use, that doesn't weaken my privacy; but if everyone knows my BIP32
xpub, that pretty much destroys my onchain privacy. Where (if anywhere)
does ChillDKG recovery data fall on this spectrum?
Thanks again!,
-Dave
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/5ce152c9181ea552b8e146c9329f011b%40dtrt.org.
next prev parent reply other threads:[~2024-07-16 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 20:05 Tim Ruffing
2024-07-16 16:43 ` David A. Harding [this message]
2024-07-16 17:31 ` Jonas Nick
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=5ce152c9181ea552b8e146c9329f011b@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=crypto@timruffing$(echo .)de \
/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