public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ali Sherief <ali@notatether•com>
To: "michaelfolkson@protonmail•com" <michaelfolkson@protonmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transcript: Online Socratic on MuSig2
Date: Sun, 11 Sep 2022 07:43:11 +0000	[thread overview]
Message-ID: <ZSUlUBf8IO0xdA3QEaw8ytaD_2qTkfEa5vtU3t6F2OTMrOSOnrl1_Gy-zL75uhpJ3M5iWjVyeyImiCqW2c1F2xfllxyVTh8cd6ImFo0kYDk=@notatether.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

Hi Michael.

I read the transcript of the Socratic and I have to say that it is quite detailed and touches a lot of problems including the well-known theft/offline problems which also has forms elsewhere such as for passwords.

My question is, do you or anyone else in the Socratic know of any research to this that's don't involve a trade-off of theft or online connectivity?

ROAST and Liquid is perhaps the farthest I know of that addresses this problem, but it's using centralized nodes right now. I was thinking, maybe these federated nodes can be decentralized into a few of these "lite nodes" managed by each service wanting a payment, that make a threshold signature out of many subscribers paying at the same time.

- Ali

[-- Attachment #2: Type: text/html, Size: 905 bytes --]

             reply	other threads:[~2022-09-11  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  7:43 Ali Sherief [this message]
2022-09-12 16:00 ` Michael Folkson
  -- strict thread matches above, loose matches on Subject: below --
2022-09-08 11:19 Michael Folkson

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='ZSUlUBf8IO0xdA3QEaw8ytaD_2qTkfEa5vtU3t6F2OTMrOSOnrl1_Gy-zL75uhpJ3M5iWjVyeyImiCqW2c1F2xfllxyVTh8cd6ImFo0kYDk=@notatether.com' \
    --to=ali@notatether$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=michaelfolkson@protonmail$(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