From: Tim Ruffing <crypto@timruffing•de>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] BIP Draft: "ChillDKG: Distributed Key Generation for FROST"
Date: Mon, 08 Jul 2024 22:05:18 +0200 [thread overview]
Message-ID: <8768422323203aa3a8b280940abd776526fab12e.camel@timruffing.de> (raw)
Jonas Nick and I have been working on a BIP draft for Distributed Key
Generation for FROST Threshold Signatures, which we would like to
propose to the community for discussion. The draft contains a
description of the design considerations, detailed usage instructions,
and a reference implementation in Python, which we intend to be the
definitive specification. The document and the code currently live at:
https://github.com/BlockstreamResearch/bip-frost-dkg
We're looking forward to feedback from the community.
Things still to do include:
* Specifying the wire format
* Test vectors
* Possibly any extensions currently mentioned as TODO in the draft
(e.g., identifiable aborts)
* Extracting the included secp256k1proto as a proper Python package
Of course, a BIP for FROST *signing* will also be required to make use
of FROST, and we know that one is in the works.
Best,
Jonas and Tim
--
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/8768422323203aa3a8b280940abd776526fab12e.camel%40timruffing.de.
next reply other threads:[~2024-07-08 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 20:05 Tim Ruffing [this message]
2024-07-16 16:43 ` David A. Harding
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=8768422323203aa3a8b280940abd776526fab12e.camel@timruffing.de \
--to=crypto@timruffing$(echo .)de \
--cc=bitcoindev@googlegroups.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