From: Michael Folkson <michaelfolkson@protonmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Transcript: Sydney Socratic on FROST w/ Jesse Posner
Date: Wed, 27 Apr 2022 12:09:19 +0000 [thread overview]
Message-ID: <PCan3h5-ltYhl4IeHEUkUEEkqbaxqkUzuZkfpui2kQsY1mPWr6-qUW65GQejzozVAfcS9MjWADsyg8kGtILkZ0XTCMmJlaijnINZ8nCE1-k=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
Hi
I thought this transcript might be of interest to the mailing list.
https://btctranscripts.com/sydney-bitcoin-meetup/2022-03-29-socratic-seminar/
Jesse Posner joined the online Sydney Socratic [1] last month to discuss his work on FROST. There is a video [2] too. As Jesse states [3] "With the introduction of Taproot, we can begin to bridge this divide between a "hot" and "cold" key by leveraging distributed key generation and threshold signing."
During the Socratic he discussed how with FROST you can simulate a threshold signature arrangement (k-of-n, k<n or indeed n-of-n) with only one signature going onchain when making a transaction. There are lots of upsides, you can swap participants in and out without needing an onchain transaction and even change the arrangement from say a 3-of-5 to a 4-of-5 without needing an onchain transaction. There are challenges too of course and it was discussed how the various participants might swap nonces and keep track of which nonce they should be using when signing, how hardware wallets might support FROST and to what extent accountability can be achieved if malicious parties are included in the threshold arrangement.
Thanks to Lloyd Fournier for organizing it and thanks to Adam Jonas for maintaining the btctranscripts.com site. The Sydney Socratic is online, open to all and Lloyd has a number of ideas for future topics.
[1]: https://github.com/bitcoin-sydney/socratic
[2]: https://rumble.com/vz3i3u-frost-the-future-of-schnorr-multisignatures-on-bitcoin.html
[3]: https://brink.dev/blog/2021/04/15/frost/
--
Michael Folkson
Email: michaelfolkson at [protonmail.com](http://protonmail.com/)
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
[-- Attachment #2: Type: text/html, Size: 5186 bytes --]
reply other threads:[~2022-04-27 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='PCan3h5-ltYhl4IeHEUkUEEkqbaxqkUzuZkfpui2kQsY1mPWr6-qUW65GQejzozVAfcS9MjWADsyg8kGtILkZ0XTCMmJlaijnINZ8nCE1-k=@protonmail.com' \
--to=michaelfolkson@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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