-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shamir's secret sharing scheme #553
Comments
Pull request? |
It's not done yet. I wanted to ask at first if it was desirable. So I'll start working on that. |
Yes! Though expect some feedback on interface and style. Note also that bx used source code generation. Maintainers can help with that once implemented if necessary. |
I’m not to keen on the incorporation of both mnemonics and encryption into this single command. The result is far too complex in relation to the bx approach. We prefer to use composition vs. overloading. I haven’t looked at implementations, but we have existing commands for key encryption and mnemonics, so I assume we could compose with them to achieve the same features with less complexity and more flexibility. |
Multi-valued outputs in bx are generally emitted as a property tree. |
@jakubtrnka did you ever get anywhere with this? I still think it's a good idea. |
Hello, |
Sounds great, let’s do it! |
I suggest adding shamir's secret sharing scheme as described Satoshi Labs's SLIP0039
My idea is to introduce command that generates n Shamir's shares with reconstruction threshold of m with m<=n. Optionally with seed encryption using passphrase.
mnemonic-to-sshare [-h ] --count <n> --threshold <m> --language <lang> [--passphrase <psh>] [WORD]...
Command produces either m shares each on separate line, or
Error: invalid mnemonic
, orError: threshold too large
Reverse command restoring mnemonic from Shamir's shares would look like this:
sshare-to-mnemonic [-h] [--passphrase <psh>] --share [WORD]... --share [WORD]... [...]
Command produces either mnemonic, or
Error: inconsistent shares
,Error: invalid share(s)
, orError: not enough shares
The text was updated successfully, but these errors were encountered: