From: Egor Zuev <zyev.egor@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP proposal: Elliptic SSS scheme
Date: Fri, 27 Nov 2020 20:12:29 +0300 [thread overview]
Message-ID: <CAFBkc6nosCtNfG=JobKHLQBccMqcB3yDmR3N8U=HJZs_rzAfzQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]
Hi everyone!
Would like to propose the solution for sharing the private key / other
sensitive information with a modified SSS scheme.
The key features are:
1) the secret restoration is not possible without corresponding signatures
2) share[i] belongs to privateKey[i] only, which means it can't be signed
with a different private key
I hope this approach can help on the application level to share sensitive
information or it can be used as m-of-n multi-signature (this is
discussable). I've attached the pdf file with the concept description. Also
here is the repo with a working example in node.js:
https://github.com/ega-forever/esss
Thanks in advance for your time.
[-- Attachment #1.2: Type: text/html, Size: 891 bytes --]
[-- Attachment #2: musig-esss.v1.pdf --]
[-- Type: application/pdf, Size: 207167 bytes --]
reply other threads:[~2020-11-27 17:12 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='CAFBkc6nosCtNfG=JobKHLQBccMqcB3yDmR3N8U=HJZs_rzAfzQ@mail.gmail.com' \
--to=zyev.egor@gmail.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